| Summary: | Regression fail // broke usage of multi server syntax | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | JianHong Yin <jiyin> |
| Component: | autofs | Assignee: | Ian Kent <ikent> |
| Status: | CLOSED WORKSFORME | QA Contact: | Filesystem QE <fs-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.5 | CC: | andreas.pfaffeneder.extern, brian, gmariene, ikent, miguel.paiva.cs |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 239361 | Environment: | |
| Last Closed: | 2013-09-06 02:35:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 239361, 1018641 | ||
| Bug Blocks: | |||
|
Comment 2
JianHong Yin
2013-09-04 03:09:43 UTC
(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 This has to have been an environmental problem at the time the test was run. This test has worked OK for me a couple of time recently, for example: https://beaker.engineering.redhat.com/jobs/488640 Ian |