GBP does not treat orphaned resources consistently
Bug #1460247 reported by
AJAY KALAMBUR
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I wanted to bring to your attention a particular behavior in GBP which is
different than other components
When I create any resource say policy action inside a particular user/tenant
and lets say that user/tenant is deleted other components like nova/neutron for instance shows project as
– because it does not exist any more
In GBP it shows the Project ID of the deleted project and does not seem to
show it as orphaned
| Changed in group-based-policy: | |
| milestone: | none → kilo-gbp-4 |
| importance: | Undecided → Medium |
| tags: | added: juno-backport-potential |
Revision history for this message
| Sumit Naiksatam (snaiksat) wrote | #1 |
| Changed in group-based-policy: | |
| status: | New → Confirmed |
| milestone: | kilo-gbp-4 → next |
To post a comment you must log in.
GBP does not get a notification for user/tenant delete. We need to explore how we can subscribe to these notifications and react.