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!
Upstream bug component is Capsule
Moving to POST since upstream bug http://projects.theforeman.org/issues/13841 has been closed
Can you provide some more detailed steps for verification?
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
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
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
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