openstack-upgrade action not working on Bionic with --channel=4.0/stable

Bug #1993717 reported by Paul Goins
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
TrilioVault Data Mover API Charm
New
Undecided
Unassigned
TrilioVault Workload Manager Charm
New
Undecided
Unassigned

Bug Description

I'm working on a trilio upgrade for a customer, but am having trouble using the openstack-upgrade action.

trilio-wlm's openstack-origin was cloud:bionic-train. I set action-managed-upgrade=true, then openstack-origin=cloud:bionic-ussuri. I then tried to run openstack-upgrade.

Here is what I got:

$ juju run-action --wait trilio-wlm/1 openstack-upgrade
unit-trilio-wlm-1:
  UnitId: trilio-wlm/1
  id: "7011"
  message: run_upgrade() got an unexpected keyword argument 'upgrade_openstack'
  results: {}
  status: failed
  timing:
    completed: 2022-10-20 15:59:09 +0000 UTC
    enqueued: 2022-10-20 15:59:08 +0000 UTC
    started: 2022-10-20 15:59:08 +0000 UTC

Relevant details from "juju status --format=yaml trilio-wlm":

  trilio-wlm:
    charm: trilio-wlm
    series: bionic
    os: ubuntu
    base: ubuntu:18.04
    charm-origin: charmhub
    charm-name: trilio-wlm
    charm-rev: 6
    charm-channel: 4.0/stable
    charm-version: eabf195

Revision history for this message
Paul Goins (vultaire) wrote (last edit ):

While I can't vouch for the cleanliness of this workaround, this seems to have worked for me:

# Reset to the previous series.
# Ideally doesn't do much aside from updating sources
# since action-managed-upgrade is True.
juju config trilio-wlm openstack-origin=cloud:bionic-train

# Disable action-managed upgrades
juju config trilio-wlm action-managed-upgrade=false

# Re-try the upgrade. Note that this affects everything
# all at once rather than 1-by-1.
juju config trilio-wlm openstack-origin=cloud:bionic-ussuri

Revision history for this message
Paul Goins (vultaire) wrote :

The same issue appears to affect charm-trilio-dm-api.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.