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.
(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