Bug 805201 - CLI should warn user if he creates DNS record with conflicting TTL values
CLI should warn user if he creates DNS record with conflicting TTL values
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Martin Kosek
IDM QE LIST
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-20 12:34 EDT by Dmitri Pal
Modified: 2016-01-29 07:54 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-29 07:54:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dmitri Pal 2012-03-20 12:34:16 EDT
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2563

In current IPA is not possible to create two different DNS records with same DNS name and different TTL.

How reproducible:
Add two different records with same name and different TTL.
It's only CLI user experince improvement.

Steps to Reproduce:
1. {{{ ipa dnsrecord-add --ttl=123 localnet r1 --a-rec=1.2.3.4 }}}
2. {{{ ipa dnsrecord-add --ttl=555 localnet r1 --txt-rec=TEST }}}

Actual results:
{{{
# ipa dnsrecord-add --ttl=123 localnet r1 --a-rec=1.2.3.4
  Record name: r1
  Time to live: 123
  A record: 1.2.3.4
# ipa dnsrecord-add --ttl=555 localnet r1 --txt-rec=TEST
  Record name: r1
  Time to live: 123
  A record: 1.2.3.4
  TXT record: TEST
}}}

Expected results:
{{{
# ipa dnsrecord-add --ttl=123 localnet r1 --a-rec=1.2.3.4
  Record name: r1
  Time to live: 123
  A record: 1.2.3.4
# ipa dnsrecord-add --ttl=555 localnet r1 --txt-rec=TEST
  Record name: r1
  Time to live: 555
  A record: 1.2.3.4
  TXT record: TEST
 Warning: It's not possible to have two records with same name and different TTL values.
}}}
Comment 2 Martin Kosek 2016-01-29 07:54:55 EST
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as WONTFIX. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.

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