Bug 2062141 - Designate DNS – not informative error message on zone import
Summary: Designate DNS – not informative error message on zone import
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-designate
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: 17.0
Assignee: Don Kehn
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-09 09:31 UTC by Arkady Shtempler
Modified: 2022-09-21 12:19 UTC (History)
4 users (show)

Fixed In Version: openstack-designate-12.0.2-0.20220614212615.f255747.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-21 12:19:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1964323 0 None None None 2022-03-09 09:31:18 UTC
OpenStack gerrit 835651 0 None master: MERGED designate: Clarifies the zone import error message (If7d50cbd4fa0ce86e0ddf03068da36acd7d72cb4) 2022-06-14 18:29:57 UTC
OpenStack gerrit 844485 0 None stable/wallaby: MERGED designate: Clarifies the zone import error message (If7d50cbd4fa0ce86e0ddf03068da36acd7d72cb4) 2022-06-14 18:30:02 UTC
Red Hat Issue Tracker OSP-13458 0 None None None 2022-03-09 09:54:53 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:19:50 UTC

Description Arkady Shtempler 2022-03-09 09:31:18 UTC
### Scenario ###
Try to import zone that is already exists.
You can use: https://review.opendev.org/c/openstack/designate-tempest-plugin/+/832215

### Actual Result ###
Zone gets into the ERROR status as expected, but the error message: “An undefined error occurred” should be improved.

API Response:
2022-03-07 14:45:44.796 232983 INFO tempest.lib.common.rest_client [req-c3cd4dce-7fc4-4589-9089- https://192.168.122.200/dns/ 0.022s
2022-03-07 14:45:44.796 232983 DEBUG tempest.lib.common.rest_client [req-c3cd4dce-7fc4-4589-9089-
        Body: None
    Response - Headers: {'date': 'Mon, 07 Mar 2022 14:45:44 GMT', 'server': 'Apache/2.4.41 (Ubuntu)', 'content-length': '384', 'content-type': 'application/json', 'x-openstack-request-id': 'req-c3cd4dce-7fc4-4589-9089-https://192.168.122.200/dns/'}
        Body: b'{"id": "7306e40d-6753-43bd-8551-message": "An undefined error occurred. ", "zone_id": null, "project_id": "https://127.0.0.1:60053/v2/"}}

Comment 3 Don Kehn 2022-04-11 19:45:29 UTC
Have developed a patch for the fix, working on unit test at the moment. This patch defines the situation where the exception handler produces the message 'An undefined error occurred' to the exception during the zone import where an underlying exception occurs from the rpc dispatcher at the same time as a duplicate zone exception. Added an exception to clarify the error msg and exception message to the rpc ExpectedException.

Comment 12 errata-xmlrpc 2022-09-21 12:19:32 UTC
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543


Note You need to log in before you can comment on or make changes to this bug.