Bug 1359125
Summary: | Smart Proxy DNS nsupdate GSS fails | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Stefan Meyer <smeyer> |
Component: | Foreman Proxy | Assignee: | Dmitri Dolguikh <ddolguik> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2.0 | CC: | bbuckingham, dmitri, inecas, jcallaha, smeyer, sthirugn, zhunting |
Target Milestone: | Unspecified | Keywords: | 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
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 |