Bug 1359125 - Smart Proxy DNS nsupdate GSS fails
Summary: Smart Proxy DNS nsupdate GSS fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.2.0
Hardware: All
OS: All
high
high
Target Milestone: Unspecified
Assignee: Dmitri Dolguikh
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-22 10:57 UTC by Stefan Meyer
Modified: 2019-09-25 21:20 UTC (History)
7 users (show)

Fixed In Version: foreman-proxy-1.11.0.5-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Satellite 6.2 Snap 21
Last Closed: 2016-08-16 07:11:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13841 0 None None None 2016-07-22 11:00:48 UTC
Foreman Issue Tracker 15865 0 None None None 2016-08-01 18:54:16 UTC
Red Hat Product Errata RHBA-2016:1615 0 normal SHIPPED_LIVE Satellite 6.2.1 bug fix update 2016-08-16 11:09:48 UTC

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


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