nova list --status invalid-status results in ERROR

Bug #1639242 reported by serlex
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Undecided
Jeffrey Zhang
Mitaka
Fix Released
Undecided
Jeffrey Zhang
Ocata
Invalid
Undecided
Jeffrey Zhang

Bug Description

Hi,

Found during tempest:

test_list_servers_detailed_filter_by_invalid_status

==============================
Failed 1 tests - output below:
==============================

tempest.api.compute.admin.test_servers.ServersAdminTestJSON.test_list_servers_detailed_filter_by_invalid_status[id-d56e9540-73ed-45e0-9b88-98fc419087eb]
--------------------------------------------------------------------------------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "tempest/api/compute/admin/test_servers.py", line 67, in test_list_servers_detailed_filter_by_invalid_status
        body = self.client.list_servers(detail=True, **params)
      File "tempest/lib/services/compute/servers_client.py", line 153, in list_servers
        resp, body = self.get(url)
      File "tempest/lib/common/rest_client.py", line 291, in get
        return self.request('GET', url, extra_headers, headers)
      File "tempest/lib/services/compute/base_compute_client.py", line 48, in request
        method, url, extra_headers, headers, body, chunked)
      File "tempest/lib/common/rest_client.py", line 665, in request
        resp, resp_body)
      File "tempest/lib/common/rest_client.py", line 829, in _error_checker
        message=message)
    tempest.lib.exceptions.ServerFault: Got server fault
    Details: The server has either erred or is incapable of performing the requested operation.

This can also be reproduced with simple command:

nova list --status invalid-status

Here is the upstream bug with a fix for nova 13.1.2

https://bugs.launchpad.net/nova/+bug/1579706

Regards,
Sercan

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

you are using mitaka branch, right?

Changed in kolla:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/394271

Revision history for this message
serlex (serlex) wrote :

Yes I'm using mitaka branch

Thank you

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

check the patch https://review.openstack.org/394271

bump the nova version will fix your issue. another quick workaround is change the configuration( kolla-build.conf ) in your environment.

[nova-base]
location=xxx

Changed in kolla:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (stable/mitaka)

Reviewed: https://review.openstack.org/394271
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=450bf6b5fd353610f79ab7200a1b20f7f12de9f5
Submitter: Jenkins
Branch: stable/mitaka

commit 450bf6b5fd353610f79ab7200a1b20f7f12de9f5
Author: Jeffrey Zhang <email address hidden>
Date: Mon Nov 7 14:04:02 2016 +0800

    Bump OpenStack service version

    Change-Id: I7ffb9b4698fd8caf516236ac07526c1586611110
    Closes-Bug: #1639242

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 2.0.3

This issue was fixed in the openstack/kolla 2.0.3 release.

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.