There is no way to specify package_upgrade: option for murano-spawned VM's
Bug #1563718 reported by
Kirill Zaitsev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
During M cycle murano added ability to install murano-agent with cloud-init. As part of this change we've added
package_upgrade: true
to cloud init configs. This lead to deploy time increases and in certain cases to murano-agent being unable to execute the execution plan. See https:/
The option has been removed, but it feels like it would be a good practice to allow user to decite whether he want s the packages upgraded or not.
We should make this option configurable, preferrably on per-instance level
| Changed in murano: | |
| assignee: | nobody → SFilatov (filatecs) |
| Changed in murano: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Kirill Zaitsev (kzaitsev) wrote | #1 |
| Changed in murano: | |
| status: | In Progress → Confirmed |
| Changed in murano: | |
| milestone: | newton-1 → newton-2 |
Revision history for this message
| Valerii Kovalchuk (vakovalchuk) wrote | #2 |
| Changed in murano: | |
| assignee: | SFilatov (filatecs) → nobody |
| Changed in murano: | |
| milestone: | newton-2 → newton-3 |
| Changed in murano: | |
| milestone: | newton-3 → newton-rc1 |
| Changed in murano: | |
| milestone: | newton-rc1 → newton-rc2 |
| Changed in murano: | |
| milestone: | newton-rc2 → ocata-1 |
| Changed in murano: | |
| milestone: | 3.1.0 → pike-2 |
| Changed in murano: | |
| milestone: | pike-2 → pike-rc1 |
To post a comment you must log in.
Please submit a patch. The bot will move the bug from Confirmed to In Progress automatically