yahoo-eng-team team mailing list archive

[Tore Anderson <tore@xxxxxx>]

Public bug reported:

The "l3-agent-list-hosting-router" command fails with the rather
unhelpful error message «Field names must be unique!» while using the
interactive Neutron CLI. The first invocation of the command never fails
the first time in a single CLI session, but after that it fails every
time. Demonstrated below:

$ neutron
(neutron) l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
+--------------------------------------+------------------------------+----------------+-------+----------+
| id                                   | host                         | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------------+----------------+-------+----------+
| 5da51291-2ec4-4cf2-8f4a-35581b17b81c | net01-osl2.os-cloud.acme.com | True           | :-)   | active   |
| ea6b71bd-5447-4ff0-87f4-58a681344c50 | net02-osl2.os-cloud.acme.com | True           | :-)   | active   |
| 7e5b7b98-ba7e-4b63-a86f-2e6a9f293c98 | net01-osl3.os-cloud.acme.com | True           | :-)   | standby  |
+--------------------------------------+------------------------------+----------------+-------+----------+
(neutron) l3-agent-list-hosting-router 7dd291f7-057a-4dff-8475-e8715c980f82
Field names must be unique!
(neutron) l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
Field names must be unique!

Exiting the CLI session and starting a new one will permit me to
successfully use the "l3-agent-list-hosting-router" command again, but
just once (after which it will start failing again in the same manner).

The problem occurs only when using an interactive Neutron CLI session,
that is, if I instead run the exact same sequence of commands directly
from the shell as command line arguments to the /usr/bin/neutron
command, it works fine:

$ neutron l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
+--------------------------------------+------------------------------+----------------+-------+----------+
| id                                   | host                         | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------------+----------------+-------+----------+
| ....normal output snipped.... 
+--------------------------------------+------------------------------+----------------+-------+----------+
$ neutron l3-agent-list-hosting-router 7dd291f7-057a-4dff-8475-e8715c980f82
+--------------------------------------+------------------------------+----------------+-------+----------+
| id                                   | host                         | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------------+----------------+-------+----------+
| ....normal output snipped.... 
+--------------------------------------+------------------------------+----------------+-------+----------+
$ neutron l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
+--------------------------------------+------------------------------+----------------+-------+----------+
| id                                   | host                         | admin_state_up | alive | ha_state |
+--------------------------------------+------------------------------+----------------+-------+----------+
| ....normal output snipped.... 
+--------------------------------------+------------------------------+----------------+-------+----------+

I am using RHEL7, openstack-neutron-7.0.1-1.el7.noarch.rpm.

Tore

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1561378

Title:
  l3-agent-list-hosting-router failing with «Field names must be
  unique!» in interactive Neutron CLI

Status in neutron:
  New

Bug description:
  The "l3-agent-list-hosting-router" command fails with the rather
  unhelpful error message «Field names must be unique!» while using the
  interactive Neutron CLI. The first invocation of the command never
  fails the first time in a single CLI session, but after that it fails
  every time. Demonstrated below:

  $ neutron
  (neutron) l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | id                                   | host                         | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | 5da51291-2ec4-4cf2-8f4a-35581b17b81c | net01-osl2.os-cloud.acme.com | True           | :-)   | active   |
  | ea6b71bd-5447-4ff0-87f4-58a681344c50 | net02-osl2.os-cloud.acme.com | True           | :-)   | active   |
  | 7e5b7b98-ba7e-4b63-a86f-2e6a9f293c98 | net01-osl3.os-cloud.acme.com | True           | :-)   | standby  |
  +--------------------------------------+------------------------------+----------------+-------+----------+
  (neutron) l3-agent-list-hosting-router 7dd291f7-057a-4dff-8475-e8715c980f82
  Field names must be unique!
  (neutron) l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
  Field names must be unique!

  Exiting the CLI session and starting a new one will permit me to
  successfully use the "l3-agent-list-hosting-router" command again, but
  just once (after which it will start failing again in the same
  manner).

  The problem occurs only when using an interactive Neutron CLI session,
  that is, if I instead run the exact same sequence of commands directly
  from the shell as command line arguments to the /usr/bin/neutron
  command, it works fine:

  $ neutron l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | id                                   | host                         | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | ....normal output snipped.... 
  +--------------------------------------+------------------------------+----------------+-------+----------+
  $ neutron l3-agent-list-hosting-router 7dd291f7-057a-4dff-8475-e8715c980f82
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | id                                   | host                         | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | ....normal output snipped.... 
  +--------------------------------------+------------------------------+----------------+-------+----------+
  $ neutron l3-agent-list-hosting-router 6fecbc74-a7f1-431a-a83d-3ab59b9c7faf
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | id                                   | host                         | admin_state_up | alive | ha_state |
  +--------------------------------------+------------------------------+----------------+-------+----------+
  | ....normal output snipped.... 
  +--------------------------------------+------------------------------+----------------+-------+----------+

  I am using RHEL7, openstack-neutron-7.0.1-1.el7.noarch.rpm.

  Tore

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