Ensure openstack-release package is correct after install hook
The linked bug shows the install of the charm with openstack-origin set
to zed. This happens because configure_installation_source() causes the
openstack-release package to be installed *before* the zed cloud archive
sources are configured into /etc/apt and an apt update done. This means
that the openstack-release package says "yoga" despite the zed packages
actually being installed.
Then, on the config-changed hook, it sees that the installed version is
showing as yoga and tries to do an upgrade. This fails, as the charm
hasn't yet bootstrapped, and the charm tries to bootstrap after
upgrading the packages.
There's a few bugs here which are exposed, but the tactical fix is to
force the openstack-release to match the installed packages.
Reviewed: https:/ /review. opendev. org/c/openstack /charm- keystone/ +/857729 /opendev. org/openstack/ charm-keystone/ commit/ 2c33c74c8fb78ec fd61060663fb7b1 a649fbd7d6
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 2c33c74c8fb78ec fd61060663fb7b1 a649fbd7d6
Author: Alex Kavanagh <email address hidden>
Date: Wed Sep 14 16:27:57 2022 +0100
Ensure openstack-release package is correct after install hook
The linked bug shows the install of the charm with openstack-origin set installation_ source( ) causes the release package to be installed *before* the zed cloud archive
to zed. This happens because configure_
openstack-
sources are configured into /etc/apt and an apt update done. This means
that the openstack-release package says "yoga" despite the zed packages
actually being installed.
Then, on the config-changed hook, it sees that the installed version is
showing as yoga and tries to do an upgrade. This fails, as the charm
hasn't yet bootstrapped, and the charm tries to bootstrap after
upgrading the packages.
There's a few bugs here which are exposed, but the tactical fix is to
force the openstack-release to match the installed packages.
Change-Id: I3f47daf6bda6b6 2ffe4152ede2709 f802f0ab606
Closes-Bug: #1989538