yahoo-eng-team team mailing list archive

[Tzach Shefi <tshefi@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1400048

Title:
  nova list --hostname invalidhostname

Status in OpenStack Compute (Nova):
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1400048/+subscriptions