openstack-upgrade action doesn't properly detect swift package upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Swift Proxy Charm |
Fix Released
|
High
|
James Page | ||
OpenStack Swift Storage Charm |
Fix Released
|
High
|
James Page |
Bug Description
Running on a xenial-pike cloud, upgrading to xenial-queens (this cloud has seen trusty-mitaka, xenial-mitaka, xenial-newton, xenial-pike, and now going to queens in the process of upgrades)
Running cs:swift-proxy-75 and getting outcome: "no upgrade available"
It appears that apt_pkg.
I added debugging and setting the following action_sets at the bottom of openstack_
action_
action_
action_
You can see apt.version_compare is returning "7" instead of the expected == 1 from the return of this function: return apt.version_
$ juju run-action --wait swift-proxy/1 openstack-upgrade
unit-swift-proxy-1:
id: 504a5617-
results:
aptcmp: "7"
outcome: no upgrade available.
swiftavail: 2.17.0
swiftcur: 2.10.2
status: completed
timing:
completed: 2019-02-23 00:57:05 +0000 UTC
enqueued: 2019-02-23 00:57:00 +0000 UTC
started: 2019-02-23 00:57:01 +0000 UTC
unit: swift-proxy/1
Thinking this meant I had to step through from netwon to ocata, I changed to ocata cloud repo and get aptcmp == 3, because it's 2.10.2 to 2.13.0 as latest in ocata, though earliest in ocata was only 2.11.0.
Fix is to change openstack_
/var/lib/
and
/var/lib/
Changed in charm-swift-proxy: | |
status: | New → Triaged |
Changed in charm-swift-storage: | |
status: | New → Triaged |
Changed in charm-swift-proxy: | |
importance: | Undecided → High |
Changed in charm-swift-storage: | |
importance: | Undecided → High |
Changed in charm-swift-proxy: | |
milestone: | none → 19.04 |
Changed in charm-swift-storage: | |
milestone: | none → 19.04 |
Changed in charm-swift-proxy: | |
assignee: | nobody → James Page (james-page) |
Changed in charm-swift-storage: | |
assignee: | nobody → James Page (james-page) |
status: | Triaged → In Progress |
Changed in charm-swift-proxy: | |
status: | Triaged → In Progress |
Changed in charm-swift-proxy: | |
status: | Fix Committed → Fix Released |
Changed in charm-swift-storage: | |
status: | Fix Committed → Fix Released |
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 680891 appears to be the documentation culprit that may have lead to this code.