Skip to content

Conversation

@dmc5179
Copy link
Contributor

@dmc5179 dmc5179 commented Apr 30, 2020

Just noticed that after provision many clusters with this tool I have hundreds of nodes listed in my RHN account. Update the provisioning tool to deregister the nodes before tearing them down. Tested several times with cluster up and down to ensure the nodes are being deregistered.

Copy link
Owner

@jaredhocutt jaredhocutt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a part where it starts all of the machines and ensures that are up (e.g. that SSH is available) before running the rhsm_unsubscribe role?

The way it is currently, if a person has their cluster shutdown and they attempt to delete it, it would fail since it would be unable to connect to their cluster.

@dmc5179
Copy link
Contributor Author

dmc5179 commented May 22, 2020

@jaredhocutt Will do. I'm a little behind on making this update but I'll certainly add it in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants