Actions
Bug #18677
closedAccepting a node by API or UI doesn't do the same things exactly
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
We miss a simple log with info level about node accepted o_O
Updated by François ARMAND about 4 years ago
- Status changed from New to In progress
Updated by François ARMAND about 4 years ago
Hum, the log is in the code, but node displayed.
Updated by François ARMAND about 4 years ago
- Subject changed from Missing log info when a node is accepted to Accepting a node by API or UI doesn't do the same things exactly
Ok, so the problem is that we don't do exactly the same things with one node or several nodes, and the API call "several nodes" even if only one is given.
Updated by François ARMAND about 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/3414
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.7 to 6.1.8
Updated by François ARMAND almost 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|6f022c026ca0f5f7cfbc4e59f53004515dd2caf5.
Updated by François ARMAND almost 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.8 and 6.2.1 which were released today.
Actions