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.
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
Comment 2Alexander Bokovoy
2018-08-30 07:20:31 UTC
Do I understand correctly that for any missing required attribute you want CLI to transform the message to show actual CLI option name instead of the actual internal attribute name? But JSON response should mention an internal attribute name because that's what is specified in the JSON request.
Alexander,
If its possible, the CLI command should display the actual CLI option instead of the actual internal attribute name
Comment 4Alexander Bokovoy
2018-08-30 15:02:22 UTC
Ok. This is not a regression and is not blocking any testing so I'd rather see it as an improvement for future releases. I can certainly see a value of doing such a change but cannot really tell right now whether it would require additional development that could be backported to RHEL 7.
Comment 5Alexander Bokovoy
2018-09-11 18:32:54 UTC
Comment 6Florence Blanc-Renaud
2018-10-16 16:55:53 UTC
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.
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