Openstack Mojo Testing

[bionic][train->ussuri] openstack upgrade: placement is not upgraded and so checks fail

Bug #1888830 reported by Alex Kavanagh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Openstack Mojo Testing
Fix Committed
Undecided
Unassigned

Bug Description

The next_openstack_upgrade train -> ussuri scenario can't complete as the placement service is not upgraded from train to ussuri. This results in failures to launch instances.

Additionally, placement doesn't have upgrade support via config-changed: https://bugs.launchpad.net/charm-placement/+bug/1884064 -- but this is in progress.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

https://github.com/openstack-charmers/zaza-openstack-tests/pull/455 should address this. Need to see if it is actually fixed.

Changed in openstack-mojo-specs:
assignee: nobody → Alex Kavanagh (ajkavanagh)
status: New → In Progress
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Is fixed by zaza-openstack-tests change and confirmed to be working in mojo openstack dashboard.

Changed in openstack-mojo-specs:
assignee: Alex Kavanagh (ajkavanagh) → nobody
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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