Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1439038 - Allow erasing ipaDomainResolutionOrder attribute
Allow erasing ipaDomainResolutionOrder attribute
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: IPA Maintainers
Ganna Kaihorodova
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-05 01:21 EDT by Jan Cholasta
Modified: 2017-08-01 05:48 EDT (History)
7 users (show)

See Also:
Fixed In Version: ipa-4.5.0-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 05:48:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Verification for bug "Allow erasing ipaDomainResolutionOrder attribute" (3.51 KB, text/plain)
2017-05-17 09:55 EDT, Ganna Kaihorodova
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2304 normal SHIPPED_LIVE ipa bug fix and enhancement update 2017-08-01 08:41:35 EDT

  None (edit)
Description Jan Cholasta 2017-04-05 01:21:58 EDT
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/6825

Currently when trying to erase the ipaDomaiResolutionOrder an internal error is raised as the code ends up calling the split() method in a None object.
Comment 4 Ganna Kaihorodova 2017-05-17 09:55 EDT
Created attachment 1279703 [details]
Verification for bug "Allow erasing ipaDomainResolutionOrder attribute"
Comment 5 errata-xmlrpc 2017-08-01 05:48:56 EDT
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/RHBA-2017:2304

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