Bug 1302567 - Running neutron net-list in Mitaka returns "list index out of range"
Running neutron net-list in Mitaka returns "list index out of range"
Product: RDO
Classification: Community
Component: python-neutronclient (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: Kilo
Assigned To: lpeer
Ofer Blaut
Depends On:
  Show dependency treegraph
Reported: 2016-01-28 03:16 EST by Udi
Modified: 2016-05-19 11:34 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-05-19 11:34:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Udi 2016-01-28 03:16:59 EST
Description of problem:
I deployed a Mitaka overcloud on CentOS 7. It was the testday version from the delorian packages installed according to https://www.rdoproject.org/testday/mitaka/milestone2/ and https://www.rdoproject.org/rdo-manager/. The overcloud was deployed with 3 controllers and 1 compute without network isolation. There were no neutron networks defined in the overcloud yet. I ran:

[stack@undercloud ~]$ neutron net-list
list index out of range

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install according to the instructions in https://www.rdoproject.org/testday/mitaka/milestone2/ and https://www.rdoproject.org/rdo-manager/
2. Deploy an overcloud without network isolation: openstack overcloud deploy --templates --control-scale 3 --compute-scale 1 --ntp-server clock.redhat.com -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
3. Source the overcloudrc file
4. Run "neutron net-list"

Actual results:
list index out of range

Expected results:
An empty net list
Comment 1 Chandan Kumar 2016-05-19 11:34:20 EDT
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.

Note You need to log in before you can comment on or make changes to this bug.