User story #11810
closed
User story #11748: Node lifecycle: add a node state
Make node state configurable in node details
Added by François ARMAND almost 7 years ago.
Updated almost 7 years ago.
Category:
Web - Config management
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.
- Status changed from New to In progress
- Assignee changed from Raphael GAUTHIER to François ARMAND
- 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
- Description updated (diff)
- Related to Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance added
- Related to deleted (Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance)
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0~beta1 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by