Bug 1725127 - [IPI] [OSP] Destroy cluster fails because it cannot find an endpoint
Summary: [IPI] [OSP] Destroy cluster fails because it cannot find an endpoint
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.z
Assignee: Maysa Macedo
QA Contact: David Sanz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-28 13:33 UTC by David Sanz
Modified: 2020-07-01 16:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: No suitable endpoint found on the service catalog for Octavia. Consequence: IPI cluster destroy fails to successfully finish. Fix: The deletion of load balancer resource is skipped when no Octavia endpoint is find. Result: All openstack resources linked to the cluster are removed.
Clone Of:
Environment:
Last Closed: 2020-07-01 16:08:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer issues 1919 0 None closed [openstack ]failed to execute destroy command 2020-08-07 17:37:39 UTC
Red Hat Product Errata RHBA-2020:2589 0 None None None 2020-07-01 16:08:47 UTC

Description David Sanz 2019-06-28 13:33:21 UTC
Description of problem:
After installing a cluster on OSP (https://rhos-d.infra.prod.upshift.rdu2.redhat.com). it cannot be deleted with this error:

$ ./openshift-install destroy cluster
FATAL No suitable endpoint could be found in the service catalog. 

DEBUG LOG:

time="2019-06-28T15:19:52+02:00" level=debug msg="OpenShift Installer v4.2.0-201906271819-dirty"
time="2019-06-28T15:19:52+02:00" level=debug msg="Built from commit 06474dd31b58a4e4299473d41a4ab85cd488ebfc"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack containers"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack load balancers"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack servers"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack trunks"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack security-groups"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack ports"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack routers"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack subnets"
time="2019-06-28T15:19:52+02:00" level=debug msg="Deleting openstack networks"
time="2019-06-28T15:19:53+02:00" level=fatal msg="No suitable endpoint could be found in the service catalog."

Version-Release number of the following components:
$ ./openshift-install version
./openshift-install v4.2.0-201906271819-dirty
built from commit 06474dd31b58a4e4299473d41a4ab85cd488ebfc
release image registry.svc.ci.openshift.org/ocp/release@sha256:b3453b8b77ee863baf3df95299db24699305f5b126c78f9b8711cd53fbc7780d


How reproducible:

Steps to Reproduce:
1.Install IPI on OSP
2.Execute cluster destroy
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 John Trowbridge 2019-06-28 13:37:52 UTC
I think this bug was introduced with code that deletes Octavia resources.

In particular, this would cause a cloud without Octavia available to fatally error:
https://github.com/openshift/installer/blob/06474dd31b58a4e4299473d41a4ab85cd488ebfc/pkg/destroy/openstack/openstack.go#L610-L613

Comment 2 David Sanz 2019-07-02 08:35:42 UTC
Verified on 4.2.0-0.nightly-2019-07-02-045036

Comment 5 errata-xmlrpc 2020-07-01 16:08:20 UTC
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:2589


Note You need to log in before you can comment on or make changes to this bug.