#7696 Correct the --srv_rec option displayed when running ipa dnsrecord-mod command
Closed: wontfix by rcritten. Opened by abbra.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1623489

Description of problem: Correct the --srv_rec option displayed when running ipa
dnsrecord-mod command
Version-Release number of selected component (if applicable):
ipa-server-4.6.4-6.el7.x86_64
sssd-1.16.2-12.el7.x86_64
package samba is not installed
pki-server-10.5.9-6.el7.noarch
selinux-policy-3.13.1-220.el7.noarch
389-ds-base-1.3.8.4-11.el7.x86_64
How reproducible: Always
Steps to Reproduce:
1. Install IPA server
2. Modify the weight and priority of dns record
ipa dnsrecord-mod apollo.test --srv-priority='1' --srv-weight='100'
--srv-port='389' --srv-target='apollo.test'
Actual results:
ipa dnsrecord-mod apollo.test --srv-priority='1' --srv-weight='100'
--srv-port='389' --srv-target='apollo.test'
ipa: ERROR: 'srv_rec' is required
Expected results: Instead it should display '-srv-rec ' is required instead of
srv_rec
[root@master ~]# ipa dnsrecord-mod --help
  SRV Record:
    --srv-rec=STR       Raw SRV records
    --srv-priority=INT  Lower number means higher priority. Clients will
                        attempt to contact the server with the lowest-numbered
                        priority they can reach.
    --srv-weight=INT    Relative weight for entries with the same priority.
    --srv-port=INT      SRV Port
    --srv-target=DNSNAMEPARAM
                        The domain name of the target host or '.' if the
                        service is decidedly not available at this domain

Metadata Update from @abbra:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1623489

This issue has been evaluated but was not considered critical:
- it was not reported through support
- it does not have any functional impact on the product.

Due to limited team capacity, we prefer closing as won't fix rather than setting wrong expectations. If this remains a critical requirement, please re-open the BZ to request a re-evaluation of the issue, citing a clear business justification.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

Metadata