Network creation ignores --project option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
High
|
Dean Troyer |
Bug Description
OS: Centos 7
devstack checkout: master 5713497aa5819f2
Today I redeployed my devstack setup (attached local.conf): the demo account only listed the public network.
Checking with the admin account, the private network is there, but belongs to the admin project. In the stack log, the correct --project option is passed to "openstack network create", but is ignored.
Some manual tests (OSC releases 3.6.0 to 3.8.0, no difference):
$ openstack --os-cloud devstack-admin --os-region RegionOne project list
+------
| ID | Name |
+------
| 3cdc60269b7b41f
| 52bc1eb6c09f401
| ac4f7a535915407
| b35c69b497e64ea
| f69f9e22f50842d
+------
$ openstack --os-cloud devstack-admin --os-region RegionOne network create --project demo test_net_ko1|grep project_id
| project_id | ac4f7a535915407
$ openstack --os-cloud devstack-admin --os-region RegionOne network create --project f69f9e22f50842d
| project_id | ac4f7a535915407
But skipping the --os* parameters the network is created on the correct project:
$ openstack network create --project f69f9e22f50842d
| project_id | f69f9e22f50842d
And using neutron CLI is OK (which is why I opened the bug here):
$ neutron --os-cloud devstack-admin --os-region RegionOne net-create --tenant-id f69f9e22f50842d
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
| tenant_id | f69f9e22f50842d
[vagrant@
| project_id | f69f9e22f50842d
Changed in python-openstackclient: | |
importance: | Undecided → High |
Changed in python-openstackclient: | |
assignee: | nobody → Dean Troyer (dtroyer) |
Changed in python-openstackclient: | |
status: | New → In Progress |
i can confirm the same.
global requirements just bumped openstackclient version to 3.8.0 and thus broke our build as well.