Bug 148981 - NETWORK tests reporting an ERROR
Summary: NETWORK tests reporting an ERROR
Alias: None
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: net (Show other bugs)
(Show other bugs)
Version: 2
Hardware: ia64 Linux
Target Milestone: ---
Assignee: Rob Landry
QA Contact: Rob Landry
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-17 18:19 UTC by Rick Hester
Modified: 2007-04-18 17:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-11 16:39:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
network tests when run from kickstart file generated by ispec (and modified for quotes and missing eth1 setup) (288.86 KB, text/plain)
2005-02-17 18:28 UTC, Rick Hester
no flags Details
network tests when run from /usr/sbin/redhat-ready (173.30 KB, text/plain)
2005-02-17 18:29 UTC, Rick Hester
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:419 normal SHIPPED_LIVE Hardware Certification Suite bug fix update 2005-05-11 04:00:00 UTC

Description Rick Hester 2005-02-17 18:19:41 UTC
Description of problem:
When running the network tests either from a ks file generated by
ispec or on by manually invoking redhat-ready, the network tests
report an error.

Two NICs are in the box - both have been setup for DHCP. See below 
for the ifconfig outputs.

Attaching the two packaged results files.

Version-Release number of selected component (if applicable):

How reproducible:
Previous runs resulted in NETWORK [FAILED], but these last
two runs resulted in NETWORK [ERROR]  seems easy enough
to reproduce. I had suspected that the earlier failures were
due to not BOOTPROTO being set for eth1 so it never received
an IP.  Once I added BOOTPROTO=dhcp to ifcfg-eth1, I stared
getting these ERROR results.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
ifconfig output:
eth0      Link encap:Ethernet  HWaddr 00:30:6E:39:46:AE
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::230:6eff:fe39:46ae/64 Scope:Link
          RX packets:13303411 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1063799095 (1014.5 MiB)  TX bytes:5736 (5.6 KiB)

[root@lincoln ~]# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:30:6E:39:C6:CD
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::230:6eff:fe39:c6cd/64 Scope:Link
          RX packets:118593 errors:0 dropped:0 overruns:0 frame:0
          TX packets:49763661 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8911495 (8.4 MiB)  TX bytes:75196814583 (70.0 GiB)

Server address:
wilson.rihes has address

Comment 1 Richard Li 2005-02-17 18:22:12 UTC
Can you upload your output.log for NETWORK?

Also, the errata update for RHR (-14a) has bugfixes in NETWORK.

Comment 2 Rob Landry 2005-02-17 18:25:50 UTC
Also, if you can start the network test with none of the interfaces
up; that can help in a multiple nic situation where both are attached
to the same network (the easiest to setup, but technically invalid if
they are both up at the same time) since the test will then properly
bring up one interface at a time and avoid having the network issues
from misdirecting traffic.

Comment 3 Rick Hester 2005-02-17 18:28:39 UTC
Created attachment 111173 [details]
network tests when run from kickstart file generated by ispec (and modified for quotes and missing eth1 setup)

Comment 4 Rick Hester 2005-02-17 18:29:47 UTC
Created attachment 111174 [details]
network tests when run from /usr/sbin/redhat-ready

Comment 5 Richard Li 2005-02-17 18:32:39 UTC
the ispec quotes problem is also fixed in the errata. are these results RPMs you
are uploading that contain the output.log file?

Comment 6 Rick Hester 2005-02-17 19:08:49 UTC

those RPMs should have the output log in them
I'm assuming that the errata you refer to - RHR (14a)
is on RHN?


I'll rerun the NETWORK test with both interfaces down.

Comment 7 Richard Li 2005-02-17 19:16:29 UTC
Yes, the errata is on RHN.

Comment 8 Rick Hester 2005-02-19 00:46:10 UTC
I haven't updated this because I have been getting very inconclusive
results.   First time I tried to run the tests with both interfaces
down, there were some "artifcacts" from previous tests that clouded
the results. So I cleand those and rebooted, but forgot that the 
install was from one of the ispec ks installs, so it came up and 
started running redhat-ready in init 4.  Since I didn't feel like 
I could stop it without leaving more artifacts, I let it run to 
completion.   This time the network test passed (puzzling since
I made no change to the eth interface status).  After that test 
completed, I got in a hurry and forgot to insure that both interfaces
were down.  Only one was.  But the test completed correctly.
Now I'm running again with both interfaces up.  But it is taking 
an abnormally longer time to complete (may be due to some network 
issues we have been experiencing).  

So, all that to tell you I can't conclusively attribe the failures
to interface status.  Still working on it - we have Monday off, so
it will be a while before I have another update.  

In the mean time, if you happen to notice anything funny in the 
logs that I've sent - please let me know.

Comment 9 Rob Landry 2005-04-14 18:02:51 UTC
Can we verify if -17beta (people.redhat.com/rlandry/rhr2/test) resolves this issue?

Comment 10 Rick Hester 2005-04-14 18:11:45 UTC

Unfortunately, we're tied up testing beta 1 of RHEL4 U1 at the 
moment.  So, I won't be able to get to the -17 beta for a while.

The other challenge is that I was finding it difficult to reliably
reproduce this problem.  

I have some certs planed for release of RHEL4 U1, so I will try
this out then.  That may be the earliest I can get to it.

I did run into other networking issues and problems after reporting
this particular one.  I was able to work around those by using
a faster cert server as well as have both the cert target and
server connected to the same switch.   So my problems may have
been performance related.

Comment 11 Richard Li 2005-05-11 16:39:36 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.