Comment 5 for bug 1273006
Revision history for this message
| Andrew Woodward (xarses) wrote Re: nodes don't return to discovered state | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
No, deleting the node from the environment is not the goal here. We want to re-set it to discovery so that we can re-deploy the node in the current environment. Usually this occurs because there was a hardware error or other issue that caused the node to fail deployment. However when you force the node back into discovery, it doesn't reset the error state so it can not be re-deployed with out going through the overly un-necessary process of deleting/removing the node (which will cause it to lose all of its configuration)
Issues:
1) If you force a node into the bootstrap discovery image, it should reset the node back to discovered state. If you subsequently start the deployment, it should re-provision and bootstrap the node as if it was the first time adding the node to the cluster
2) You should be able to reset a node with out deleting it from the DB and cluster (I.E. It should maintain its Role, ID, Interface mappings