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.
DescriptionWaldirio M Pinheiro
2016-04-14 10:18:13 UTC
Description of problem:
Actually is possible do this configuration according kcs https://access.redhat.com/articles/1527913, btw after the kerberos ticket expire, Satellite 6 don't update the same., so will be necessary implement this rfe.
Version-Release number of selected component (if applicable):
6.1.8
How reproducible:
100%
Steps to Reproduce:
1. Configure environment according kcs
2. Execute test with nsupdate or creating a new machine via Sat6
3. Wait the ticket expiration time (or just force)
4. Execute the same test using nsupdate
Actual results:
tkey query failed: GSSAPI error: Major = Unspecified GSS failure. Minor code may provide more information, Minor = Ticket expired.
Expected results:
new entry in dns over AD.
Additional info:
Is this actually a bug?
We renew the ticket on every request (an aside -- there's a bug filed against realm smart-proxy module because this is inefficient: https://bugzilla.redhat.com/show_bug.cgi?id=1133940). All I'm seeing here is output from cli commands that shows what happens when a kerberos ticket expires (and how to manually fix this issue), but not logs from smart-proxy.
As I mentioned above, it's not clear to me that this is actually a bug report. The attached logs illustrate a *manual* walk-through using cli tools, but there's no information about the user encountering this issue when using smart-proxy.
Moreover, smart-proxy does handle ticket expiry (if a too aggressively), I don't believe this to be an issue.