Activity log for bug #1624978

Date Who What changed Old value New value Message
2016-09-19 04:43:25 Paul bug added bug
2016-09-19 04:43:25 Paul attachment added skip_field_validation_none.patch https://bugs.launchpad.net/bugs/1624978/+attachment/4743362/+files/skip_field_validation_none.patch
2016-09-19 05:12:06 Paul description The fix for bug #1522989 broke the list command if no VMs are running. When the list of VMs is empty there are no fields to validate so specifying fields always returns an error. Field validation should be skipped if there are no VMs to make the behaviour of "nova list --fields" consistent with "nova list" ~$ nova list --fields metadata,created,networks +--------------------------------------+------------------------------------------------------------+----------------------+----------------------------------- ----------------------+ | ID | Metadata | Created | Networks | +--------------------------------------+------------------------------------------------------------+----------------------+----------------------------------- ----------------------+ | 4072c7c5-eab4-45f3-a3b8-1b0d010ddf7c | {u'instance': u'my-instance', u'vnfc-type': u'management'} | 2016-09-19T03:11:13Z | internal-network=10 .0.0.3, 192.168.2.68 | +--------------------------------------+------------------------------------------------------------+----------------------+----------------------------------- ----------------------+ ~$ nova list --fields metadata,created,networks ERROR (CommandError): Non-existent fields are specified: [u'metadata', u'created', u'networks'] ~$ nova list +----+------+--------+------------+-------------+----------+ | ID | Name | Status | Task State | Power State | Networks | +----+------+--------+------------+-------------+----------+ +----+------+--------+------------+-------------+----------+ The fix for bug #1522989 broke the list command if no VMs are running. When the list of VMs is empty there are no fields to validate so specifying fields always returns an error. Field validation should be skipped if there are no VMs to make the behaviour of "nova list --fields" consistent with "nova list" With VMs running: ~$ nova list --fields metadata,created,networks +--------------------------------------+------------------------------------------------------------+----------------------+----------------------------------- ----------------------+ | ID | Metadata | Created | Networks | +--------------------------------------+------------------------------------------------------------+----------------------+----------------------------------- ----------------------+ | 4072c7c5-eab4-45f3-a3b8-1b0d010ddf7c | {u'instance': u'my-instance', u'vnfc-type': u'management'} | 2016-09-19T03:11:13Z | internal-network=10 .0.0.3, 192.168.2.68 | +--------------------------------------+------------------------------------------------------------+----------------------+----------------------------------- ----------------------+ No VMs running: ~$ nova list --fields metadata,created,networks ERROR (CommandError): Non-existent fields are specified: [u'metadata', u'created', u'networks'] ~$ nova list +----+------+--------+------------+-------------+----------+ | ID | Name | Status | Task State | Power State | Networks | +----+------+--------+------------+-------------+----------+ +----+------+--------+------------+-------------+----------+
2016-11-08 07:53:49 Arvinder Singh python-novaclient: assignee Arvinder Singh (arvinder-singh)
2016-11-10 08:13:31 Arvinder Singh python-novaclient: status New Confirmed
2016-11-10 10:20:24 OpenStack Infra python-novaclient: status Confirmed In Progress
2017-03-11 15:42:07 OpenStack Infra python-novaclient: assignee Arvinder Singh (arvinder-singh) Diana Clarke (diana-clarke)
2017-03-14 01:35:46 Diana Clarke python-novaclient: assignee Diana Clarke (diana-clarke)
2017-03-28 14:02:56 OpenStack Infra python-novaclient: assignee Diana Clarke (diana-clarke)
2017-03-28 16:44:22 OpenStack Infra python-novaclient: status In Progress Fix Released