Red Hat Bugzilla – Bug 1314085
[DOCS] Adding cloud provider tries to delete node
Last modified: 2016-03-09 12:09:45 EST
Section Number and Name:
CHAPTER 10. CONFIGURING FOR AWS
Describe the issue:
Switching from not using a cloud provider to using a cloud provider produces the error message (or at least one similar)  because the node switched from using the hostname as the externalID (which would have been the case when no cloud provider was being used) to using the AWS instance-id (which is what the AWS cloud provider specifies).
Suggestions for improvement:
The fix is to login as a cluster-admin and delete the node(s) `oc delete node <NODE_IDENTIFIER>` and everything will be fine as the new node identifier will take charge. Engineering suggested the simpler fix to this situation is to add this fact to the documentation.
Recording NodeReady event message for node XXXX.ec2.internal
Attempting to register node XXXX.ec2.internal
Previously "XXXX.ec2.internal" had externalID "YYYY"; now it is "XXXX.ec2.internal"; will delete and recreate.
Unable to delete old node: User "system:node:XXXX.ec2.internal" cannot delete nodes at the cluster scope
Work in progress:
@Eric-please review and let me know if this satisfies the request
@Ashley, the idea will meet the request once it goes through, but there were some in-line comments made before I got there and I responded to a few of them.
Commits pushed to master at https://github.com/openshift/openshift-docs
Bug 1314085, added guidance: switching to cloud provider tries to delete the node
Merge pull request #1695 from ahardin-rh/config-aws
Bug 1314085, switching to cloud provider tries to delete the node
Content is now published: