Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

replacing a failed infra causes the new one to be unregistered #370

Open
ioggstream opened this issue Jul 11, 2017 · 0 comments
Open

replacing a failed infra causes the new one to be unregistered #370

ioggstream opened this issue Jul 11, 2017 · 0 comments

Comments

@ioggstream
Copy link
Contributor

Reproduce

  • I have 2 infra nodes
infra-0
infra-1
  • infra-1 fails, I mark it unhealty and update the stack
o stack resource mark unhealthy  shift...infra... 1
o stack update shift --existing
  • a new infra-1 is created
  • the old infra-1 is removed

I expect

  • deployment-bastion-node-cleanup to be run against the old node, if present

Instead

  • deployment-bastion-node-cleanup references infra-1 by hostname, so it will unregister the new node
ioggstream added a commit to ioggstream/openshift-on-openstack that referenced this issue Jul 11, 2017
@ioggstream
fix redhat-openstack#370: run deployment_bastion_node_cleanup only on…
825021d 
… the same server uuid.
@ioggstream ioggstream mentioned this issue Jul 11, 2017
Open
ioggstream added a commit to ioggstream/openshift-on-openstack that referenced this issue Aug 11, 2017
@ioggstream
fix redhat-openstack#370: run deployment_bastion_node_cleanup only on…
88d0dbf 
… the same server uuid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ioggstream