[SRU] Backport Fix barbican client with application credentials/trusts to Ussuri/Victoria
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Ussuri |
Triaged
|
Medium
|
Unassigned | ||
Victoria |
Triaged
|
Medium
|
Unassigned | ||
Wallaby |
Triaged
|
Medium
|
Unassigned | ||
octavia (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Incomplete
|
Medium
|
David Negreira |
Bug Description
[Impact]
* Users cannot add an HTTPS endpoint with octavia/barbican when using application credentials (it returns http error 500).
[Test Case]
* Full details of commands in comment #10, summary below.
* Add a user in a project
* Add the admin role to the user in the project
* Create application credentials
* Create a barbican certificate store
* Create octavia loadbalancer and listener with the application credentials
[Where problems could occur]
* Users might not be able to create load balancers or attach a listener to a load balancer.
[Other Info]
* Original story: https:/
* Upstream fix and backports: https:/
* Current upstream fix for octavia/Ussuri: https:/
* Current upstream fix for octavia/Victoria:https:/
no longer affects: | octavia |
no longer affects: | octavia (Ubuntu) |
description: | updated |
Changed in cloud-archive: | |
status: | New → Fix Released |
Changed in octavia (Ubuntu): | |
status: | New → Fix Released |
this is just a placeholder atm until the upstream backports are merged