Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1359125

Summary: Smart Proxy DNS nsupdate GSS fails
Product: Red Hat Satellite Reporter: Stefan Meyer <smeyer>
Component: Foreman ProxyAssignee: Dmitri Dolguikh <ddolguik>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: bbuckingham, dmitri, inecas, jcallaha, smeyer, sthirugn, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: foreman-proxy-1.11.0.5-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Satellite 6.2 Snap 21
Last Closed: 2016-08-16 07:11:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefan Meyer 2016-07-22 10:57:54 UTC 
Description of problem:
After updating from 6.1.9 nsupdate fails with error message "wrong number of arguments"

This looks like this bug:
http://projects.theforeman.org/issues/13841

After applying the patch manually it works as expected.

Version-Release number of selected component (if applicable):
foreman-proxy.noarch 1.11.0.4-1.el7sat


How reproducible:


Steps to Reproduce:
1. Install Satellite 6.2 Snap 21
2. Configure nsupdate GSS 
3. Create new system

Actual results:
DNS creation fails with error message:
E, [2016-07-22T12:22:00.546663 #11231] ERROR -- : wrong number of arguments (0 for 1)
D, [2016-07-22T12:22:00.546710 #11231] DEBUG -- : wrong number of arguments (0 for 1) (ArgumentError)
/usr/share/foreman-proxy/modules/dns_nsupdate/dns_nsupdate_gss_main.rb:20:in `nsupdate_connect'
...

Expected results:
DNS entry should be created correctly

Additional info:
This will affect all customers using IPA or MS DNS servers to create dns entries!
Comment 1 Bryan Kearney 2016-07-22 12:16:29 UTC 
Upstream bug component is Capsule
Comment 2 Bryan Kearney 2016-07-22 12:16:30 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/13841 has been closed
Comment 4 jcallaha 2016-08-09 20:40:29 UTC 
Can you provide some more detailed steps for verification?
Comment 5 Dmitri Dolguikh 2016-08-12 09:49:28 UTC 
To verify the fix you'll need to configure smart-proxy's dns module to use kerberised version of nsupdate (nsupdate_gss) and try to create or delete a dns record
Comment 6 jcallaha 2016-08-12 19:05:10 UTC 
Verified in Satellite 6.2.1 Snap 1.2


# echo -e "server 192.168.100.1\n \
update add abc.rhq.lab.eng.bos.redhat.com 3600 IN A 192.168.100.10\n \
send\n" | nsupdate -k /etc/rndc.key


# nslookup abc.rhq.lab.eng.bos.redhat.com 192.168.100.1
Server:		192.168.100.1
Address:	192.168.100.1#53

Name:	abc.rhq.lab.eng.bos.redhat.com
Address: 192.168.100.10
Comment 7 Stefan Meyer 2016-08-12 19:10:49 UTC 
The procedure to use an IPA server for DNS management is documented in [1], subsection 4.3.5.3 GSS-TSIG DNS.

While it is not documented in the Satellite 6.2 documentation, it worked fine with 6.1.x.

[1] https://theforeman.org/manuals/1.10/index.html#4.3.5DNS
Comment 9 errata-xmlrpc 2016-08-16 07:11:33 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.

https://access.redhat.com/errata/RHBA-2016:1615