Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/6203

This is how dnsrecord-add behaves in 4.4:
{{{
$ ipa dnsrecord-add example.test test --srv-target $HOSTNAME
ipa: ERROR: invalid 'srvrecord': 'srv_priority' is a required part of DNS record
}}}

This is how it behaved before 4.4:
{{{
$ ipa dnsrecord-add example.test test --srv-target $HOSTNAME
SRV Priority: 
...
}}}

Marking as regression - in 7.2 the interactive prompt worked.

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/afea9616318fbbffc2c296b7c41890db8595e3cc
https://fedorahosted.org/freeipa/changeset/dce95a14595a37ce83bcf3e28f41feab715d0c81
https://fedorahosted.org/freeipa/changeset/38a51fa984a6aa92f383d7f8176057de8e057d52
ipa-4-4:
https://fedorahosted.org/freeipa/changeset/fa8a5c33b73398c731cf2a472c79bd9a51404fe2
https://fedorahosted.org/freeipa/changeset/b4c104ee9038d8d87a7e78137826e655ebb5d39b
https://fedorahosted.org/freeipa/changeset/47d6f49e53d27e1df1377a91789c072b11ccea31

Created attachment 1201161 [details]
evidence

verified 
4.4.0-11

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://rhn.redhat.com/errata/RHBA-2016-2404.html