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.
Bug 804572 - Irrelevant error message when per-part modification mode is used during dnsrecord-mod operation without specifying the record.
Summary: Irrelevant error message when per-part modification mode is used during dnsre...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 09:58 UTC by Gowrishankar Rajaiyan
Modified: 2015-05-20 15:22 UTC (History)
2 users (show)

Fixed In Version: ipa-2.2.0-6.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2012-06-20 13:24:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0819 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2012-06-19 20:34:17 UTC

Description Gowrishankar Rajaiyan 2012-03-19 09:58:51 UTC
Description of problem:
This was reported by NC as part of IPA DNS Enh test day-2.

Version-Release number of selected component (if applicable):
ipa-server-2.2.0-4.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. [root@primenova ~]# ipa dnsrecord-mod lab.eng.pnq.redhat.com test5 --a-ip-address=10.65.201.190
  

Actual results:
ipa: ERROR: no modifications to be performed

Expected results:
We should raise an relevant error message when per-part modification mode is used without specifying the record. (--a-rec= in this case)

Additional info:

Comment 2 Gowrishankar Rajaiyan 2012-03-19 11:01:11 UTC
Also, as part of negative testing the following message is displayed

[root@primenova ~]# ipa dnsrecord-add lab.eng.pnq.redhat.com bumblebee --cname-hostname=zetaprime.lab.eng.pnq.redhat.com --cname-rec=
  
Actual results:
ipa: ERROR: an internal error has occurred

Comment 3 Martin Kosek 2012-03-19 11:01:46 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2551

Comment 7 Gowrishankar Rajaiyan 2012-03-29 09:12:50 UTC
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ipa-dns-181: Bug 804572 - Irrelevant error message when per-part modification mode is used during dnsrecord-mod operation without specifying the record.
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: closes https://engineering.redhat.com/trac/ipa-tests/ticket/374
:: [   LOG    ] :: verifies https://bugzilla.redhat.com/show_bug.cgi?id=804572
:: [   LOG    ] :: Executing: ipa dnsrecord-add lab.eng.pnq.redhat.com bumblebee --cname-hostname=zetaprime.lab.eng.pnq.redhat.com --cname-rec=
:: [   LOG    ] :: "ipa dnsrecord-add lab.eng.pnq.redhat.com bumblebee --cname-hostname=zetaprime.lab.eng.pnq.redhat.com --cname-rec=" failed as expected.
:: [   PASS   ] :: Error message as expected: ipa: ERROR: invalid 'cname_hostname': Raw value of a DNS record was already set by cname_rec option
:: [   LOG    ] :: Executing: ipa dnsrecord-mod lab.eng.pnq.redhat.com test5 --a-ip-address=10.65.201.190
:: [   LOG    ] :: "ipa dnsrecord-mod lab.eng.pnq.redhat.com test5 --a-ip-address=10.65.201.190" failed as expected.
:: [   PASS   ] :: Error message as expected: ipa: ERROR: 'arecord' is required
:: [   LOG    ] :: Duration: 10s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: ipa-dns-181: Bug 804572 - Irrelevant error message when per-part modification mode is used during dnsrecord-mod operation without specifying the record.
report saved as: /tmp/rhts.report.31396.txt
================ final pass/fail report =================
   Test Date: Thu Mar 29 03:36:08 EDT 2012 
   Total : [2] 
   Passed: [2] 
   Failed: [0] 
   Abort : [0]
---------------------------------------------------------


Verified: ipa-server-2.2.0-7.el6.x86_64

Comment 9 Martin Kosek 2012-04-25 09:22:33 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 11 errata-xmlrpc 2012-06-20 13:24:52 UTC
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.

http://rhn.redhat.com/errata/RHBA-2012-0819.html


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