Actions
User story #11810
closed
User story #11748: Node lifecycle: add a node state
Make node state configurable in node details
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Effort required:
Name check:
Fix check:
Regression:
Description
We need to have a drop down list + submit in node details to change the node state (and so, not be forced to use an API request).
Also add a label in node list for non default state so that we can quickly find these nodes.
Updated by François ARMAND about 7 years ago
- Status changed from New to In progress
- Assignee changed from Raphael GAUTHIER to François ARMAND
Updated by François ARMAND about 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1812
Updated by François ARMAND about 7 years ago
- Related to Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance added
Updated by François ARMAND about 7 years ago
- Related to deleted (Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance)
Updated by François ARMAND about 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|e4ccb354f64eeb184abbc55ecdad446c44e7be2f.
Updated by Vincent MEMBRÉ almost 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0~beta1 which was released today.
- 4.3.0~beta1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions