Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1071439[details]
sssd_no_ptr.log
Description of problem:
This looks like a regression, tests are failing to update the ptr record using the ad provider.
Version-Release number of selected component (if applicable):
sssd-client-1.13.0-26.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. realm join sssd2012r2.com
2. check AD for the PTR record
3.
Actual results:
A record exists, PTR does not
Expected results:
A record and PTR record exits
Additional info:
(In reply to Pavel Reichl from comment #4)
> Dan, do I understand it correctly that it seems that we have changed default
> value of dyndns_update option for AD from true to false?
I checked the source code of sssd-1.13.0-26.el7.x86_64 and the default value for dyndns_update_ptr is TRUE; it was not changed.
My understanding is that ptr record is not updated even though it should be.
Hello. According the last log you do not have configured IPv6 reverse zone in AD. Quick look to AD DNS configuration confirms that - I can see only IPv4 zone in there.
(In reply to Petr Spacek from comment #15)
> Hello. According the last log you do not have configured IPv6 reverse zone
> in AD. Quick look to AD DNS configuration confirms that - I can see only
> IPv4 zone in there.
That's wrong approach. Many users could have configured just a IPv4 reverse zone.
Because they do not care about IPv6 on server side. But clients can have IPv6 addresses which new sssd will try to use in nsupdate.
It worked before an update and does not work aftert an upgrade. That's really bad user experience and moreover customers can notice it after a long time. The right approach will be to update just parts which can be updated (IPv4 in this case)
Okay then, in that case we have to fix a bug in nsupdate.
nsupdate apparently exists on GSSAPI failure when called with option -g and does not process other command blocks (separated by 'send' command).
This is different than behavior for other errors where nsupdate just skips the block which failed and continues with the next block of commands.
Reproducer:
Store this in a file called "upd":
update add nsupdate.test.redhat.com 666 IN A 192.0.2.1
send
update add nsupdate.test.redhat.com 666 IN TXT "HELLo!"
send
And compare output from following commands:
$ nsupdate /tmp/upd
update failed: REFUSED
update failed: REFUSED
$ nsupdate -g /tmp/upd
tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Server DNS/xxx not found in Kerberos database.
You can see that first run without GSSAPI tried both command blocks but the second run with GSSAPI failed on first command block and did not continue.
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://rhn.redhat.com/errata/RHSA-2015-2355.html
Created attachment 1071439 [details] sssd_no_ptr.log Description of problem: This looks like a regression, tests are failing to update the ptr record using the ad provider. Version-Release number of selected component (if applicable): sssd-client-1.13.0-26.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. realm join sssd2012r2.com 2. check AD for the PTR record 3. Actual results: A record exists, PTR does not Expected results: A record and PTR record exits Additional info: