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

Bug 1724652

Summary:	[RFE] Alow force deletion of in PENDING entities
Product:	Red Hat OpenStack	Reporter:	Andreas Karis <akaris>
Component:	openstack-octavia	Assignee:	Assaf Muller <amuller>
Status:	CLOSED WONTFIX	QA Contact:	Bruna Bonguardo <bbonguar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	cgoncalves, gkadam, gthiemon, ihrachys, lpeer, majopela, scohen
Target Milestone:	---
Target Release:	---
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:	2019-07-03 15:56:01 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 Andreas Karis 2019-06-27 13:24:05 UTC

Description of problem:
Currently, PENDING_UPDATE and PENDING_CREATE entities cannot be deleted. Please allow a force delete, as the only workaround currently is to connect to the database and run e.g.:
~~~
MariaDB [octavia]> update load_balancer set provisioning_status = 'ACTIVE' where provisioning_status = 'PENDING_UPDATE';
Query OK, 1 row affected (0.37 sec)
Rows matched: 1  Changed: 1  Warnings: 0

MariaDB [octavia]> 
~~~

And then delete those entities once set to ACTIVE. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Account for the fact that entities may be stuck in PENDING and a force delete is needed.

Comment 1 Gregory Thiemonge 2019-07-03 15:56:01 UTC

Hi Andreas,

Force deletion of LB is not a good idea and is dangerous, it has been discussed upstream in the following story: https://storyboard.openstack.org/#!/story/2002568

We are currently working on solution to mitigate this issue:
- Updating timeout values (users may think a load balancer is stuck while timeouts have not expired yet): https://bugzilla.redhat.com/show_bug.cgi?id=1726733
- Avoid unnecessary service restarts on deployment stack update: https://bugzilla.redhat.com/show_bug.cgi?id=1726735
- Graceful shutdown/restart of octavia containers: https://bugzilla.redhat.com/show_bug.cgi?id=1726738

Comment 2 Andreas Karis 2019-07-03 20:56:15 UTC

I don't think that this is just a timeout issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1712448
https://bugzilla.redhat.com/show_bug.cgi?id=1724798

I ran into these 2 issues above where loadbalancers never left the PENDING state.

Comment 3 Carlos Goncalves 2019-07-04 07:19:53 UTC

RHBZ #1712448 was indeed a bug (already fixed upstream) but it was not leaving resources actually stuck in PENDING_*. It might have given that impression but a closer look showed that there was a bug when an invalid certificate is passed in, the LB was going into ERROR and Octavia after some time tried to repair it.

RHBZ #1724798 does not have resources in a transient state (PENDING_*). I had a quick look at the logs yesterday and I could see them in a non-PENDING status. We will triage it there sometime soon.