commit 21d212cb2739a3ff1b08d8d96916dfd638f06ffe
Author: Alex Kavanagh <email address hidden>
Date: Wed Aug 7 15:09:13 2019 +0100
Ensure that keystone service is paused if needed on series upgrade
During series upgrade, the keystone packages get re-installed as the
underlying Linux has been upgraded and new package sets are updated and
then pulled in. For trusty->xenial this means that keystone.service
gets enabled which then breaks haproxy. On install, on xenial+, the
keystone.service is disabled in the install hook. This just replicates
this in the series-upgrade hook.
Reviewed: https:/ /review. opendev. org/675127 /git.openstack. org/cgit/ openstack/ charm-keystone/ commit/ ?id=21d212cb273 9a3ff1b08d8d969 16dfd638f06ffe
Committed: https:/
Submitter: Zuul
Branch: master
commit 21d212cb2739a3f f1b08d8d96916df d638f06ffe
Author: Alex Kavanagh <email address hidden>
Date: Wed Aug 7 15:09:13 2019 +0100
Ensure that keystone service is paused if needed on series upgrade
During series upgrade, the keystone packages get re-installed as the service is disabled in the install hook. This just replicates
underlying Linux has been upgraded and new package sets are updated and
then pulled in. For trusty->xenial this means that keystone.service
gets enabled which then breaks haproxy. On install, on xenial+, the
keystone.
this in the series-upgrade hook.
Change-Id: Ic5ed6cf354d554 5b9e554e205a048 955a381e0f5
Closed-Bug: #1839021