Skip to content

Drop use of SWIFT_CODENAMES when determining currently installed Swift version#915

Open
mpanduru wants to merge 1 commit intojuju:masterfrom
mpanduru:swift-upgrade
Open

Drop use of SWIFT_CODENAMES when determining currently installed Swift version#915
mpanduru wants to merge 1 commit intojuju:masterfrom
mpanduru:swift-upgrade

Conversation

@mpanduru
Copy link
Copy Markdown

Since the SWIFT_CODENAMES and PACKAGE_CODENAMES are not maintained as of Wallaby, the currently installed version of Swift should be determined similarly to how it is done for other OpenStack packages: by identifying the current release using the openstack-release package.
The current approach causes Swift upgrades from source versions subsequent to Victoria to fail to be detected.

Fixes: #914

…t version

Since the SWIFT_CODENAMES and PACKAGE_CODENAMES are not maintained as of Wallaby, the currently installed version of Swift should be determined similarly to how it is done for other OpenStack packages: by identifying the current release using the openstack-release package.

The current approach causes Swift upgrades from source versions subsequent to Victoria to fail to be detected.


Fixes: juju#914
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Swift upgrade from versions subsequent to Victoria fail to be detected due to missing codename mapping

1 participant