Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1623540

Summary:	[RFE] Option to delete cascade load balancers
Product:	Red Hat OpenStack	Reporter:	Carlos Goncalves <cgoncalves>
Component:	openstack-octavia-ui	Assignee:	Carlos Goncalves <cgoncalves>
Status:	CLOSED ERRATA	QA Contact:	Bruna Bonguardo <bbonguar>
Severity:	low	Docs Contact:
Priority:	low
Version:	13.0 (Queens)	CC:	ihrachys, jschluet, lpeer, majopela, rszmigie
Target Milestone:	z6	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-octavia-ui-1.0.1-4.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1695602 (view as bug list)		Environment:
Last Closed:	2019-04-30 17:23:43 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:	1695602

Description Carlos Goncalves 2018-08-29 15:02:38 UTC

Users may want to delete an entire load balancer including child resources like listeners, pools, members and health monitors for convenience or because of load balancers ending up in an immutable state (e.g. failed failover) that prevent users from adding/updating/removing child resources.

Octavia API and CLI offer a LB delete cascade option that does just that. Such option should be possible to trigger via the Horizon dashboard too.

Comment 1 Carlos Goncalves 2018-10-08 09:24:14 UTC

Leaving untriaged for now so that the squad can prioritize and target to an appropriate OSP version.

Comment 9 errata-xmlrpc 2019-04-30 17:23:43 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-2019:0926