Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1314085

Summary: [DOCS] Adding cloud provider tries to delete node
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: DocumentationAssignee: Ashley Hardin <ahardin>
Status: CLOSED CURRENTRELEASE QA Contact: Eric Jones <erjones>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: urgent    
Version: 3.1.0CC: aos-bugs, erjones, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
OpenShift 3.1 AP 3.1
Last Closed: 2016-03-09 17:09:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Jones 2016-03-02 21:23:36 UTC 
Document URL: 
https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#configuring-for-aws

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) [0] 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.

Additional information: 
[0] 
...
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
...
Comment 3 Ashley Hardin 2016-03-04 20:24:30 UTC 
Work in progress:
https://github.com/openshift/openshift-docs/pull/1695

@Eric-please review and let me know if this satisfies the request
Comment 4 Eric Jones 2016-03-04 22:13:51 UTC 
@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.
Comment 5 openshift-github-bot 2016-03-07 18:32:22 UTC 
Commits pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/e37a2d59ade0918ebbf9360aebaba804a4e4e9a9
Bug 1314085, added guidance: switching to cloud provider tries to delete the node

https://github.com/openshift/openshift-docs/commit/479d94d5ca03d14952e971d2f388f7eb71457793
Merge pull request #1695 from ahardin-rh/config-aws

Bug 1314085, switching to cloud provider tries to delete the node
Comment 6 Ashley Hardin 2016-03-09 17:09:45 UTC 
Content is now published:
https://docs.openshift.com/enterprise/3.1/install_config/configuring_aws.html#aws-applying-configuration-changes

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#aws-applying-configuration-changes