Bug 1796479
Summary: | [OCP43][OSP][Installer] Cluster destroy causes floating IP address being deleted | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Rafal Szmigiel <rszmigie> |
Component: | Installer | Assignee: | Mike Fedosin <mfedosin> |
Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | low | ||
Priority: | low | CC: | m.andre, mfedosin, moddi, pprinett |
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-04 11:28:06 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
Rafal Szmigiel
2020-01-30 14:28:24 UTC
Could you paste the command you used to create the API floating IP originally? It will help us understanding why your FIP was destroyed. The API's FIP has been created outside of the installer using OpenStack's CLI: $ openstack floating ip create --floating-ip-address 192.168.202.52 --project ocp4 public then it was configured as the following: (...) platform: openstack: cloud: openstack computeFlavor: rht.ocp4node externalDNS: null externalNetwork: public lbFloatingIP: 192.168.202.52 (...) Once I destroyed the cluster (after failed installation) I've noticed that 192.168.202.52 is gone. As it is "external" resource to the installer IMO it shouldn't be deleted. Fix is on review: https://github.com/openshift/installer/pull/3025 Verified on 4.4.0-0.nightly-2020-01-31-144949 Cluster deletion is not deleting the floating ip Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |