Description of problem: Client reported that on OSP 10, when encountering errors, the messages provided by the "openstack" commands are at times much less meaningful than their older counterparts (neutron, nova, etc.) In this case the "network" plugin. For example when encountering a quota on total number of rbac, we get the following error : ~~~ openstack network rbac create --action access_as_external --target-project e308b6b702ea46918752cdaeb932bff8 --type network ce629dbc-b24b-4d57-b988-81879db62eea HttpException: Conflict ~~~ Whereas the equivalent "neutron" command gives us more explanation : ~~~ neutron rbac-create --target-tenant e308b6b702ea46918752cdaeb932bff8 --action access_as_external --type network ce629dbc-b24b-4d57-b988-81879db62eea Quota exceeded for resources: ['rbac_policy']. ~~~ Version-Release number of selected component (if applicable): OSP 10 How reproducible: All the time Actual results: Non meaningful error. Expected results: The same error message as the neutron cli returns Additional info: Acknowledged that the we are still in a transition state to the openstack cli. https://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html
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