Comment 17 for bug 2039604

I started reading through the logs from Aliaksandr above (from https://bugs.launchpad.net/charm-barbican/+bug/2039604/comments/11 ). Starting with aodh:

> aodh/0, aodh/1 succesfully upgraded.
> aodh/2 stayed on Victoria.
> Worked around with:
> juju run-action aodh/2 openstack-upgrade

aodh/0 succeeded, and I see this:

```
WARNING unit.aodh/0.juju-log server.go:316 Package openstack-release has no installation candidate.
WARNING unit.aodh/0.juju-log server.go:316 Package openstack-release has no installation candidate.
INFO unit.aodh/0.juju-log server.go:316 Performing OpenStack upgrade to wallaby.
INFO unit.aodh/0.juju-log server.go:316 Installing [] with options: ['--option=Dpkg::Options::=--force-confold']
INFO unit.aodh/0.juju-log server.go:316 Upgrading with options: ['--option', 'Dpkg::Options::=--force-confnew', '--option', 'Dpkg::Options::=--force-confdef']
INFO unit.aodh/0.juju-log server.go:316 Installing ['aodh-api', 'aodh-evaluator', 'aodh-expirer', 'aodh-notifier', 'aodh-listener', 'python3-aodh', 'libapache2-mod-wsgi-py3', 'python3-apt', 'memcached', 'python3-memcache', 'haproxy', 'apache2'] with options: ['--option', 'Dpkg::Options::=--force-confnew', '--option', 'Dpkg::Options::=--force-confdef']
WARNING unit.aodh/0.juju-log server.go:316 Package python-aodh has no installation candidate.
WARNING unit.aodh/0.juju-log server.go:316 Package python-memcache has no installation candidate.
WARNING unit.aodh/0.juju-log server.go:316 DEPRECATION: should not use port_map parameter in APIConfigurationAdapter.__init__()
WARNING unit.aodh/0.juju-log server.go:316 DEPRECATION: should not use service_name parameter in APIConfigurationAdapter.__init__()
WARNING unit.aodh/0.juju-log server.go:316 Not adding haproxy listen stanza for aodh-api_int port is already in use
WARNING unit.aodh/0.juju-log server.go:316 Not adding haproxy listen stanza for aodh-api_public port is already in use
INFO unit.aodh/0.juju-log server.go:316 Deferring DB sync to leader
```

Note that this is _before_ the config-changed hook. (the upgrade should not happen until the openstack-origin config is updated) There are some other differences; see the attached diff image in the next comment.

aodh/2 failed to upgrade, and the above was not present.
Although it was present about 25m later, which I guess was Aliaksandr manually running the openstack-upgrade action?