Comment 8 for bug 1596594

I just ran into this bug On a cloud that was liberty, now mitaka. Was 17.02 charms, I stepped the openstack environment up to 17.08 charms, then I switched to the 17.11 keystone and mysql charms, and neutron-api leader went crazy with this while at 17.08 charms connecting to percona-cluster 17.11 (current cs:percona-cluster charm) in the shared-db-relation-changed hook.

I'm not sure why this is happening now, because the openstack-origin has stayed cloud:trusty-mitaka through the 17.02 to 17.08 charm upgrade and now with the 17.11 charms, still not doing an upgrade.

Maybe there's something that's an artifact of the prior upgrade that triggers the need to upgrade the db for neutron in the charm.