nova list --host invalidhostname

[Tzach Shefi]

Versions:

rhel 7
python-nova-2014.1.3-9.el7ost.noarch
openstack-nova-compute-2014.1.3-9.el7ost.noarch
openstack-nova-novncproxy-2014.1.3-9.el7ost.noarch
openstack-nova-common-2014.1.3-9.el7ost.noarch
python-novaclient-2.17.0-2.el7ost.noarch

FYI my setup is an HA deployment, but same happens on none HA.

Description of bug:
When running nova list --host with an invalid hostname (no such server or typo in server name), we should get an error.
Today we get an empty table, alerting user to the fact that an invalid host name was given would be better IMHO :)

[root@mace83935b075d6 ~(openstack_admin)]# nova list --host noSuchServer
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+
[root@mace83935b075d6 ~(openstack_admin)]# hostname
mace83935b075d6.example.com
[root@mace83935b075d6 ~(openstack_admin)]# nova list --host mace83935b075d6.example.com
+--------------------------------------+---------+--------+------------+-------------+--------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+---------+--------+------------+-------------+--------------------------------+
| 620ce9ae-2767-4f7b-a555-aa59fe10dd6b | tshefi3 | ERROR | - | NOSTATE | |
| 5b7750d1-8b0f-4fc1-8199-885317e2d5cf | tshefi4 | ACTIVE | - | Running | floating-362-main=10.35.184.24 |
+--------------------------------------+---------+--------+------------+-------------+--------------------------------+

Steps to reproduce:
1. Boot up an instance
2. #nova list --host FakeServerName -> you will get an empty table, without notice of invalid hostname
3. #nova list --host realServername you will see instance name in table as should.

[Tzach Shefi (tshefi)]

FYI same issue on Juno , just checked now.

openstack-nova-compute-2014.2-2.el7ost.noarch
openstack-nova-api-2014.2-2.el7ost.noarch
python-novaclient-2.20.0-1.el7ost.noarch
..

[Santhosh Peddiboyina (peddiboyina-9)]

Hello Tzach Shefi
I have fixed this bug, but not able to publish it to the gerrit board(some problem while updating the contact information in the ICLA agreement). I have dropped a message in the Gerrit IRC, now waiting for the reply.

[Ritesh Paiboina (rsritesh)]

I think their is not a issue with the python nova client.

When nova client list out for specific host , it makes the following request

1) FakeServerName

GET http://172.16.73.58:8774/v2/615890e1ca3d4cdfb75de7148e5d1b3c/servers/detail?host=FakeServerName

2) RealServerName

GET http://172.16.73.58:8774/v2/615890e1ca3d4cdfb75de7148e5d1b3c/servers/detail?host=RealServerName

So it happens to be that , nova has to return some error message or invalid host message to the client.

Lets see more on this.

[Zhen Qin (zqinit)]

I have submitted a fix. Please review it. Thanks!
https://review.openstack.org/#/c/255047/