Bug 1746369
| Summary: | [IPI] [OSP] Deleted openstack instance is recreated but never gets Ready status as OCP node | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | David Sanz <dsanzmor> |
| Component: | Cloud Compute | Assignee: | Mike Fedosin <mfedosin> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Sanz <dsanzmor> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | agarcial, brad.ison, egarcia, jchaloup, m.andre, mfedosin, mpatel, pprinett |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | osp | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-20 15:34:55 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1748263 | ||
|
Description
David Sanz
2019-08-28 09:52:02 UTC
I don't think this is a guarantee we make at the moment -- that you can delete an instance backing a machine directly at the infrastructure provider, outside Kubernetes, and get a new functioning replacement without manual intervention. The problem here is that the hostname for the new instance is the same as it was previously, and a node by that name already exists. But, even if that weren't the case, the Machine object will already have a nodeRef set, so the cluster-machine-approver will still refuse to approve the CSR. You would have to manually approve the CSR in this case. So far we cannot fix it in 4.2, because the necessary logic will be implemented by machine-api-operator in 4.3 only, when the healthchecker component is activated. See: https://coreos.slack.com/archives/CBZHF4DHC/p1567432430029700?thread_ts=1567430585.028900&cid=CBZHF4DHC the workaround is to remove the failed machine manually. it explained here https://github.com/openshift/installer/pull/2305 I've proposed a fix that just returns an error if we want to recreate an instance with the old name https://github.com/openshift/cluster-api-provider-openstack/pull/62 It doesn't really fix the problem, as the manual intervention is required anyway, but I hope it solves https://bugzilla.redhat.com/show_bug.cgi?id=1748263, because after the manual master deletion a new one comes up automatically, and etcd work fine after that. So, my suggestion is either to move the target to 4.3 or close this bug as invalid Moved to 4.3, because we have to fix https://bugzilla.redhat.com/show_bug.cgi?id=1748263 first and can't do this without cluster-etcd-operator component which will appear only in 4.3. Defer to 4.4, since this bz is dependent on https://bugzilla.redhat.com/show_bug.cgi?id=1748263 which was deferred to 4.4 You can close this BZ. Behaviour has changed on >= 4.3, instances deleted from OSP are only recreated if a MachineHealthCheck object is present on the cluster. Instances are created and they join correctly the cluster, so this bugzilla has no sense now The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |