Bug 1459332
| Summary: | Lack of specificity of the error messages from openstack command | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Marc Methot <mmethot> |
| Component: | python-openstackclient | Assignee: | Julie Pichon <jpichon> |
| Status: | CLOSED ERRATA | QA Contact: | Roee Agiman <ragiman> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 10.0 (Newton) | CC: | apevec, augol, beth.white, jschluet, lhh, srevivo, tfreger |
| Target Milestone: | Upstream M3 | Keywords: | Triaged |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | python-openstackclient-3.13.0-0.20180109064941.8c5f755.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-27 13:31:22 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
Marc Methot
2017-06-06 20:12:16 UTC
Unfortunately, "fixing all the error messages" is a bit too vague and difficult to resolve, it is better to open a bug about a specific message in order to get it fixed (cf. also https://bugs.launchpad.net/python-openstackclient/+bug/1554302 ). It appears the one mentioned in the description is now resolved (and likely applies to all the 'network' commands): $ openstack network rbac create --action access_as_external --target-project 6210656262954848a7ff0fc27a7e0201 --type network ed5848fd-8f1d-4d1e-b842-61b9ee7cfbfa HttpException: Conflict (HTTP 409) (Request-ID: req-8f5ef45f-7259-4927-abae-efb48e1071ff), Quota exceeded for resources: ['rbac_policy']. Based on this I'm going to mark this one as resolved, though please feel free to open more targeted bugs as you find new problematic messages. 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-2018:2086 |