Change of default behaviour, retrofit-action fails if latest LTS image not available
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-octavia-diskimage-retrofit |
Fix Released
|
High
|
Frode Nordahl |
Bug Description
During the 20.05 cycle we prepared for new LTS by adding the ``retrofit-series`` configuration option.
The default for this configuration option is determined at run time by looking up distro-info data using the ``distro-info`` command to get the latest LTS.
Previously the charm was hard coded to choose Bionic 18.04 images.
Now that Focal 20.04 LTS is out, a side effect of this change is that the retrofit action stops working unless the user has configured their glance-
While it is great to be on the edge and move users over to the mots recent release as quickly as possible this change of default behavior might be problematic.
Do we need a fall back to bionic or at the very least release note the new behavior?
Changed in charm-octavia-diskimage-retrofit: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 20.05 |
Changed in charm-octavia-diskimage-retrofit: | |
status: | Fix Committed → Fix Released |
https:/ /review. opendev. org/#/c/ 727189/