glance-registry configuration not removed on upgrade

[Chris MacNaughton]

When upgrading to an OpenStack release that doesn't support the glance-registry, configuration is left behind. At some later point, glance-api's startup command is updated to include the entire /etc/glance configuration directory, which causes glance to bind to port 9191 instead of 9292 (as configured), which causes a failure of the Glance API services in the deployed cloud

[Billy Olsen (billy-olsen)]

Need to remove the *registry* files from the /etc/glance directory (or at least move them to .bak, .old, etc)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-glance/+/873509

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/charm-glance/+/873509
Committed: https://opendev.org/openstack/charm-glance/commit/ef5d6de61564f3f81037f7082454a95ba11eedbb
Submitter: "Zuul (22348)"
Branch: master

commit ef5d6de61564f3f81037f7082454a95ba11eedbb
Author: Guillaume Boutry <email address hidden>
Date: Mon Feb 13 09:12:47 2023 +0100

    Backup glance registry configuration files on upgrade >= Stein

    Glance Registry has been deprecated in Stein release.
    Leftover configuration files can still be read and
    configure wrong settings, breaking deployment.

    Closes-Bug: 1979090
    Change-Id: I54b72aef0fd49b036cf1783ef9887fa9243c93f8