octane upgrade-control fails on removing patches from old cluster

Bug #1495963 reported by Sergey Murashov on 2015-09-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack

Bug Description

Steps to reproduce:
1) Try to switch control plane from 6.1 cics to 7.0 cic via octane upgrade-control <orig_id> <seed_id>

Actual result:
2015-09-15 12:27:59 INFO octane.util.subprocess Started process ovs-vsctl[at node-1]: ovs-vsctl del-port br-floating br-floating--br-ex │·························
2015-09-15 12:27:59 ERROR octane.util.subprocess ovs-vsctl[at node-1] stderr: ovs-vsctl: no port named br-floating--br-ex │·························
2015-09-15 12:27:59 INFO octane.util.subprocess Process ovs-vsctl finished with return value 1 │·························
2015-09-15 12:27:59 ERROR octane Command 'ovs-vsctl' returned non-zero exit status 1

Changed in fuel:
assignee: nobody → Fuel Octane Dev Team (fuel-octane)
Changed in fuel:
status: New → Incomplete
Oleg S. Gelbukh (gelbuhos) wrote :

This bug appeared because fuel-octane script incorrectly identified bridge provider as OVS while it is actually provided by linux bridge.

This is fixed by correcting version to compare to: https://review.openstack.org/#/c/223607/

Changed in fuel:
status: Incomplete → Fix Committed
milestone: none → 7.0-updates
importance: Undecided → Critical
tags: added: upgda
tags: added: feature-upgrade
removed: upgda
tags: added: module-octane
Changed in fuel:
assignee: Registry Administrators (registry) → Fuel Octane (fuel-octane-team)
Curtis Hovey (sinzui) on 2017-04-13
Changed in fuel:
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers