To summarize my last comment, when upgrading a cloud that has keystone-ldap deployed as a subordinate to keystone from bionic-queens to bionic-rocky with the command:
The above errors are seen. I believe that keystone openstack-upgrade will need to check if keystone-ldap is a subordinate, or if the packages are installed, and install python3-ldappool so that when keystone is restarted on the openstack-upgraded version, the ldap plugin doesn't fail to load.
workaround is to also run the command "juju run -a keystone 'apt-get install -y python3-ldappool".
Going to unsub field-crit and sub field-medium, as this affects LTS upgrades from bionic-queens to focal-ussuri.
To summarize my last comment, when upgrading a cloud that has keystone-ldap deployed as a subordinate to keystone from bionic-queens to bionic-rocky with the command:
juju config keystone openstack- origin= cloud:bionic- rocky
The above errors are seen. I believe that keystone openstack-upgrade will need to check if keystone-ldap is a subordinate, or if the packages are installed, and install python3-ldappool so that when keystone is restarted on the openstack-upgraded version, the ldap plugin doesn't fail to load.
workaround is to also run the command "juju run -a keystone 'apt-get install -y python3-ldappool".
Going to unsub field-crit and sub field-medium, as this affects LTS upgrades from bionic-queens to focal-ussuri.