python-muranoclient can attempt to delete the wrong package when asked to update
Bug #1448135 reported by
Kirill Zaitsev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-muranoclient |
Fix Released
|
High
|
Kirill Zaitsev | ||
| Kilo |
Fix Released
|
High
|
Kirill Zaitsev | ||
| Liberty |
Fix Released
|
High
|
Kirill Zaitsev | ||
Bug Description
Due to the fact, that murano now has non-unique fqpn and due to the fact, that during update python-muranoclient attempts to delete a package by name — there is a chance, that it will not delete the correct package.
To reproduce:
import 2 packages in different tennants,
attempt to import a package in one of those tennats with --exists-action=u, than in another.
It actually can be random, due to lack of any sorting done during pkg fetching.
| Changed in murano: | |
| milestone: | none → kilo-rc2 |
| affects: | murano → python-muranoclient |
| Changed in python-muranoclient: | |
| milestone: | kilo-rc2 → none |
| milestone: | none → 0.5.8 |
| Changed in python-muranoclient: | |
| importance: | Undecided → High |
| assignee: | nobody → Kirill Zaitsev (kzaitsev) |
| status: | New → Confirmed |
Revision history for this message
| Serg Melikyan (smelikyan) wrote | #1 |
Revision history for this message
| Serg Melikyan (smelikyan) wrote | #2 |
To post a comment you must log in.
Merged in stable/kilo https:/