replacing a failed infra causes the new one to be unregistered - Githubissues

redhat-openstack / openshift-on-openstack

A place to write templates, docs etc. for deploying OpenShift on OpenStack.

Apache License 2.0

136 stars 87 forks source link

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

Open ioggstream opened 7 years ago

ioggstream commented 7 years ago

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