Hide Forgot
Description of problem: If user modifies DNS record from uppercase to lowercase or vice-versa, then operation fails with error 'ipa: ERROR: Type or value exists:' It takes two operation to change case of record. # ipa dnsrecord-show testrelm.test _kerberos Record name: _kerberos TXT record: testrelm.test # ipa dnsrecord-mod testrelm.test _kerberos --txt-rec=TESTRELM.TEST ipa: ERROR: Type or value exists: First step is to change original value to some temp value and then temp value to desired value. # ipa dnsrecord-mod testrelm.test _kerberos --txt-rec=INTERIMTESTRELM.TEST Record name: _kerberos TXT record: INTERIMTESTRELM.TEST # ipa dnsrecord-mod testrelm.test _kerberos --txt-rec=testrelm.test Record name: _kerberos TXT record: testrelm.test Version-Release number of selected component (if applicable): ipa-server-4.2.0-15.el7_2.6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Add DNS record 2. Modify DNS record from uppercase to lowercase or vice-versa 3. Observe failure 3. Perfom two steps to achieve desired result # ipa dnsrecord-mod testrelm.test _kerberos --txt-rec=INTERIMTESTRELM.TEST Record name: _kerberos TXT record: INTERIMTESTRELM.TEST # ipa dnsrecord-mod testrelm.test _kerberos --txt-rec=testrelm.test Record name: _kerberos TXT record: testrelm.test Actual results: DNS record modification takes two operations to change case of value Expected results: DNS record modification should be able to handle change case in single operation.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/3998
IPA is using inappropriate LDAP matching rule to handle TXT (and almost all other) record types. This should be handled by DS syntax plugin.
This issue is not planned to be fixed in upcoming FreeIPA upstream release - 4.4. The status of the effort could be checked in upstream ticket in comment 2.
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux. Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX. To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution