OpenStack Keystone Charm

  1. Bug #1989538
  2. Comment #2

Comment 2 for bug 1989538

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote : Re: keystone bootstrap fail on latest/edge

The charm, on the first config-changed tries to do an openstack upgrade because it thinks it needs to do an upgrade; instrumenting the `openstack_upgrade_available` function:

unit-keystone-0: 12:00:23 INFO unit.keystone/0.juju-log openstack_upgrade_available:
unit-keystone-0: 12:00:23 INFO unit.keystone/0.juju-log ..src is cloud:jammy-zed
unit-keystone-0: 12:00:24 INFO unit.keystone/0.juju-log ..cur_vers: 2022.1
unit-keystone-0: 12:00:24 INFO unit.keystone/0.juju-log ..avail_vers = 2022.2
unit-keystone-0: 12:00:24 INFO unit.keystone/0.juju-log ..test = True
unit-keystone-0: 12:00:24 INFO unit.keystone/0.juju-log Performing OpenStack upgrade to zed.
unit-keystone-0: 12:00:24 INFO unit.keystone/0.juju-log DEPRECATION WARNING: Function configure_installation_source is being removed on/around 2017-07 : use charmhelpers.fetch.add_source() instead.
unit-keystone-0: 12:00:25 INFO unit.keystone/0.juju-log Installing [] with options: ['--option=Dpkg::Options::=--force-confold']

e.g. cur_vers is 2022.1 vs 2022.2 as being available. Time to work out what's gone wrong.