Unexpected response in agent-list command with --field param

Bug #1271948 reported by Marcos Lobo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Marcos Lobo
python-neutronclient
Fix Released
Low
Unassigned

Bug Description

On Neutron Havana (server and client). If you read the documentation about agent-list command you can read this:

# neutron help agent-list
...
  -F FIELD, --field FIELD
                        specify the field(s) to be returned by server, can be
                        repeated
...

I think there is a problem with "--field FIELD" parameter. If you try this command you obtain an unexpected response:

# neutron agent-list --field agent_type
'alive'

I think 'alive' is NOT the expected response for that request. I was expected to obtain something like:

# neutron agent-list --field agent_type
+--------------------+
| agent_type |
+--------------------+
| DHCP agent |
| Open vSwitch agent |
+--------------------+

But, if you try to obtain "alive" field, the response is the expected one.

# neutron agent-list --field alive
+-------+
| alive |
+-------+
| :-) |
| :-) |
+-------+

Changed in neutron:
assignee: nobody → Marcos Lobo (marcos-fermin-lobo)
Revision history for this message
Sridhar Gaddam (sridhargaddam) wrote :

This problem is not seen in the latest ice-house code. As you mentioned in the bug, it may be applicable only for Havana.

Revision history for this message
Marcos Lobo (marcos-fermin-lobo) wrote :

This patch has been merged https://review.openstack.org/#/c/70363/

I don't know why there are no changes (Status or Milestone) on this post...

Changed in neutron:
status: New → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → juno-1
status: Fix Committed → Fix Released
Kyle Mestery (mestery)
Changed in neutron:
importance: Undecided → Low
Changed in python-neutronclient:
importance: Undecided → Low
milestone: none → 2.3.5
status: New → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: juno-1 → 2014.2
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.