Hide Forgot
Hi Ian, can not sure if is bug, maybe case code not adapt,, please check.
beaker JOB link: https://beaker.engineering.redhat.com/jobs/486719
(In reply to Yin.JianHong from comment #2) > beaker JOB link: > https://beaker.engineering.redhat.com/jobs/486719 You need to specify which test motivated you to place this bug. AFAICS, for the above link, the failures are: - bz346091 - failed because it detected a NULL procedure call which is expected now due to ongoing, and needed changes. - bz495895 - has always been a problem since IPv6 interfaces have been present. The check for how many DNS lookups are expected is wrong and I've been unable has to fix it several times now. Just how many DNS lookup we should see is questionable as well, but the original problem had many, much more than is seen in the log of the test run. IOW, the actual result of the test result is acceptable. bz239361, bz239370 - looks like transient DNS lookup failures. I didn't see those failures in a recent run that I did so I have to concluded this is some glitch in the environment at the time of the test runs. - bz212249 - looks like it might be a regression of some sort and does warrant investigation. But which of these bugs should be used to follow up with it I don't know? Ian
Didn't see this one before but from the log: bz481139-READY kadmin: GSS-API (or Kerberos) error while initializing kadmin interface Authenticating as principal root/admin with password. That doesn't look like an autofs failure to me. Perhaps it's a regression in Kerberos or something in Kerberos has changed. The Kerberos usage in the test has worked OK for quite a while so I'm not sure what's going on.
I've run this test a couple of times lately and haven't seen this fail. Kerberos failures can be caused by name resolution difficulties, as we saw in other tests from the run above, or system time not being correct. For example, this test run worked OK: https://beaker.engineering.redhat.com/jobs/488642