Hide Forgot
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:
Moving 6.2 bugs out to sat-backlog.
Ppstream ticket: http://projects.theforeman.org/issues/17319
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.
Upstream bug component is Capsule
Upstream bug component is DHCP & DNS
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.
Closing due to lack of data + so far, it doesn't look as a bug. Please re-open the bug or file a new one if the data are available.