[SRU] Loadbalacer stuck in status PENDING_DELETE if TLS storage unavailable in cascade deletion
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Ubuntu Cloud Archive | Status tracked in Epoxy | |||||
Antelope |
In Progress
|
Undecided
|
Hua Zhang | |||
Bobcat |
In Progress
|
Undecided
|
Unassigned | |||
Caracal |
New
|
Undecided
|
Unassigned | |||
Dalmatian |
Fix Released
|
Undecided
|
Unassigned | |||
Epoxy |
Fix Released
|
Undecided
|
Unassigned | |||
Yoga |
New
|
Undecided
|
Unassigned | |||
octavia |
Fix Released
|
Undecided
|
Evgeniy Bykov | |||
octavia (Ubuntu) | Status tracked in Plucky | |||||
Focal |
Won't Fix
|
Undecided
|
Unassigned | |||
Jammy |
In Progress
|
Undecided
|
Hua Zhang | |||
Noble |
In Progress
|
Undecided
|
Hua Zhang | |||
Oracular |
Fix Released
|
Undecided
|
Unassigned | |||
Plucky |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Loadbalacer stuck in status PENDING_DELETE if TLS cert unavailable
[Test Case]
Pls refer to [Test steps] section below.
[Regression Potential]
The fix is already in the upstream main, stable/2024.1, stable/2023.2, stable/2023.1 branches, so it is a clean backport and might be helpful for deployments using octavia.
I also test this fix, it works well - https:/
[Others]
Original Bug Description Below
===========
Loadbalacer stuck in status PENDING_DELETE if TLS cert unavailable
1. Create load balancer with TERMINATED_HTTPS listener
2. Disable your TLS storage, or delete cert from storage
3. Try to delete loadbalancer with cascade flag
Error on logs:
```
Unable to retrieve certificate(s) due to Could not retrieve certificate: <some id>
Exception during message handling
```
```
Traceback (most recent call last):
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
File "/var/lib/
```
[Test steps]
1. Create load balancer with TERMINATED_HTTPS listener, eg:
secret1_
octavia_
openstack acl user add -u $octavia_user_id $secret1_id
subnetid=
lb_id=$(openstack loadbalancer create --name lb1 --vip-subnet-id $subnetid -f value -c id); echo $lb_id
listener_
2. Disable your TLS storage, or delete cert from storage, eg:
openstack secret delete $secret1_id
3. Try to delete loadbalancer with cascade flag
openstack loadbalancer delete lb1 --cascade
Here are the detailed steps for me to reproduce the problem - https:/
Changed in octavia: | |
status: | New → In Progress |
Changed in octavia: | |
assignee: | nobody → Evgeniy Bykov (lydina-pavuh) |
OpenStack Infra (hudson-openstack) wrote Fix merged to octavia (master) | #2 |
Changed in octavia: | |
status: | In Progress → Fix Released |
OpenStack Infra (hudson-openstack) wrote Fix proposed to octavia (stable/2023.1) | #3 |
Fix proposed to branch: master /review. opendev. org/c/openstack /octavia/ +/926564
Review: https:/