Bug 1478287
| Summary: | python-openstackclient doesn't show project id of security groups | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Rhys Oxenham <roxenham> |
| Component: | python-openstackclient | Assignee: | Julie Pichon <jpichon> |
| Status: | CLOSED ERRATA | QA Contact: | Honza Pokorny <hpokorny> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 11.0 (Ocata) | CC: | apevec, beth.white, hpokorny, lhh, mariel, nlevinki, srevivo, tvignaud |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-openstackclient-3.12.0-0.20170728181821.f67ebce.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
When showing the list of Neutron security groups, the Project column referenced the tenant ID instead of the project ID. This caused the Project column to appear blank. This fix changes the behavior of the operation to get the project ID, and now the list of Neutron security groups shows the relevant project ID in the Project column.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-13 21:49:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rhys Oxenham
2017-08-04 08:15:11 UTC
Thank you for the bug report. This appears to be fixed in 3.10 in Pike/OSP12. I also proposed an Ocata backport upstream in the background, we'll see how it goes. For the record, the Ocata backport also merged upstream ( https://review.openstack.org/#/c/493884/ ) and should be included in the next OSP11 rebase. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462 |