yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74652
[Bug 1791812] Re: Neutron client does not correctly deal with incorrect tenant-id when creating security group
"neutron" CLI does not look up a project name against keystone. This is
the current behavior and considering the situation that neutron CLI is
frozen for future removal we don't change its behavior.
If you want CLI to resolve a project name into UUID, please use
"openstack" CLI.
** Project changed: neutron => python-neutronclient
** Changed in: python-neutronclient
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1791812
Title:
Neutron client does not correctly deal with incorrect tenant-id when
creating security group
Status in python-neutronclient:
Won't Fix
Bug description:
When creating a Security Group with the neutron client using the
--tenant-id parameter no error occurs if you use the project name vs
UUID. It will show on the neutron security-group-list with the name vs
the UUID and does not show in Horizon. Verified on Pike.
Example:
neutron security-group-create --tenant-id physics test
neutron security-group-list
remote_group_id: 82a68de6-90ce-46bc-a73d-76a77b688bc5 |
| afd13a35-c826-4924-b01b-b5654641e816 | default | physics | egress, IPv4 |
| | | | egress, IPv6 |
| | | | ingress, IPv4, remote_group_id: afd13a35-c826-4924-b01b-b5654641e816 |
| | | | ingress, IPv6, remote_group_id: afd13a35-c826-4924-b01b-b5654641e816 |
| db952361-9ffd-4e28-92a9-fc7e10653bef | default | 982714c4b33b4c5ca0830c2fcbada89d | egress, IPv4 |
| | | | egress, IPv6 |
| | | | ingress, IPv4, remote_group_id: db952361-9ffd-4e28-92a9-fc7e10653bef |
To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1791812/+subscriptions
References