Description of problem: Destroying the cluster using: $ ./openshift-install destroy cluster --dir config/ deletes FIP allocated for OCP's API. In my opinion IP should not be deleted but unassigned. In other case deleted IP address can be taken over by other OSP user what will require DNS reconfiguration if one is re-creating the cluster. Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. Configure and create the cluster 2. Delete the cluster 3. Observe that Floating IP address configured for API doesn't exist anymore Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Cluster destroy causes API's FIP being deleted. Expected results: Floating IP address previously assigned for OCP API should be unassigned and still bounded to the project where it was originally created. Additional info: Please attach logs from ansible-playbook with the -vvv flag
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