nova-live-migration evacuation tests fail with "error: unrecognized arguments: --force"

Bug #1819166 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Critical
sean mooney

Bug Description

Seen here:

http://logs.openstack.org/50/633350/16/check/nova-live-migration/86f6551/job-output.txt.gz#_2019-03-08_09_20_42_237644

2019-03-08 09:20:42.237644 | primary | 2019-03-08 09:20:42.237 | error: unrecognized arguments: --force

The nova-live-migration job runs evacuate tests and forces one of them to bypass a down libvirt to triggera failed evacuate. It uses the nova CLI which defaults to the latest microversion and since we released python-novaclient 13.0.0 the 2.68 microversion is supported which removed the --force option on the evacuate command, and the test fails. We just need to use 2.67 on the command line.

Changed in nova:
assignee: nobody → Matt Riedemann (mriedem)
status: Triaged → In Progress
Matt Riedemann (mriedem)
Changed in nova:
assignee: Matt Riedemann (mriedem) → sean mooney (sean-k-mooney)
Revision history for this message
Eric Fried (efried) wrote :

This is why we do libs before rc.

Revision history for this message
Eric Fried (efried) wrote :
Changed in nova:
assignee: sean mooney (sean-k-mooney) → Eric Fried (efried)
Matt Riedemann (mriedem)
Changed in nova:
assignee: Eric Fried (efried) → sean mooney (sean-k-mooney)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/641986
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=30550d3d947e13f4d23b207ff96373971710dd55
Submitter: Zuul
Branch: master

commit 30550d3d947e13f4d23b207ff96373971710dd55
Author: Sean Mooney <email address hidden>
Date: Fri Mar 8 11:48:58 2019 +0000

    update gate test for removal of force evacuate

    micro-version 2.68 removed force evacuation, this chage
    updates gate/test_evacuate.sh to use micro-version 2.67

    Closes-Bug: #1819166

    Change-Id: I44a3514b4b0ba1648aa96f92e896729c823b151c

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 19.0.0.0rc1

This issue was fixed in the openstack/nova 19.0.0.0rc1 release candidate.

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.