Bug 627043
| Summary: | HWCert: RedHat v7-1.2-16 network test on sit0 interface fails on RHEL6.0 beta2 (snap10) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | IBM Bug Proxy <bugproxy> | ||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Guangze Bai <gbai> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 1.2 | CC: | czhang, gbai, jkachuck, rlandry, sdenham, tao, yshao, yuchen | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | ppc64 | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
In v7 1.2, a problem has been observed that network test included sit0 interface which is not necessarily required for testing. This issue has been fixed in v7 1.3, now sit0 interface is no longer planned nor executed during network testing.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-05-09 16:15:39 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
IBM Bug Proxy
2010-08-24 22:40:47 UTC
Created attachment 440789 [details]
network test output
The test appears to fail because no /etc/sysconfig/network-scripts/ifcfg-sit0 file appears to have been created. ------- Comment From tpnoonan.com 2010-08-25 12:58 EDT------- (In reply to comment #4) > The test appears to fail because no > /etc/sysconfig/network-scripts/ifcfg-sit0 file appears to have been created. what should ibm do? ------- Comment From lnx1138.ibm.com 2010-08-25 13:08 EDT------- (In reply to comment #5) > (In reply to comment #4) > > The test appears to fail because no > > /etc/sysconfig/network-scripts/ifcfg-sit0 file appears to have been created. > > what should ibm do? IMO, the tester needs to configure ipv6 to get the sit0 interface ------- Comment From hienn.com 2010-09-07 15:54 EDT------- The machine p7 (8233-E8B) has problem to install snap12. So, I cannot try the suggestion on the machine. However, I tried Red Hat's system-config-network utility on another system, but it doesn't have option to configure sit interfaces. My question is it is required that network test should include sit0 interface (IPV6 tunnel to IPV4 - that is not default for network) ? Generally speaking sit0 would not be required testing. The required testing is for the hardware NIC or the virtual hardware NIC as applicable. If this in turn requires sit0 or for some reason is itself called sit0 then proper configuration & testing of sit0 would be required. (The latter case would likely cause other delay for name space collision.) ------- Comment From hienn.com 2010-09-17 17:17 EDT------- I reinstalled snap13 and just marked configure network as IUV4. sit0 has not been shown up. ------- Comment From hienn.com 2010-09-23 18:22 EDT------- Retested with RHEL6 RC1 with V7-1.2-25. At beginning, when doing V7 plan, v7 print. sit0 not shown up. But when running network tet. I promped me "do you want to testst0 (y/n). If saying no, it quit the test, sying yes: it adding sit0 interface together with eth0, eth1, and sit0 always fails. ------- Comment From hienn.com 2010-09-23 18:37 EDT------- Retested with RHEL6 RC1 with V7-1.2-25. At beginning, when doing V7 plan, v7 print. sit0 not shown up. But when running network test. It promped me "do you want to test sit0 (y/n). If saying no, it quit the test, saying yes: it adding sit0 interface together with eth0, eth1, and sit0 always fails. Is there hardware associated with sit0 or just the ipv4/6 tunnel?
The '--disable --device sit0' and/or '--device {not sit0}' should allow for control of which device(s) get tested.
Can we get a copy of the results rpm, including the info and failed network runs?
------- Comment From lxie.com 2010-09-27 09:57 EDT------- (In reply to comment #16) > Is there hardware associated with sit0 or just the ipv4/6 tunnel? > > The '--disable --device sit0' and/or '--device {not sit0}' should allow for > control of which device(s) get tested. > > Can we get a copy of the results rpm, including the info and failed network > runs? After disabling sit0, network test went fine. Do you still need a copy of the failed network results rpm and etc? I don't think that should not be needed. With the confirmation that disabling sit0 works, I think we can add sit* to the list of interfaces to ignore in v7. Greg does this sound like a reasonable idea? ------- Comment From hienn.com 2010-09-27 11:23 EDT------- The problem can be resolved with options --disable --device sit0 when doing network test. (In reply to comment #12) > I don't think that should not be needed. With the confirmation that disabling > sit0 works, I think we can add sit* to the list of interfaces to ignore in v7. > > Greg does this sound like a reasonable idea? Yes. I believe the end result is sit0 should be added to the ignore list for network interfaces. Created attachment 475442 [details]
network test patch adding "sit" to the list of interfaces to ignore
------- Comment From lxie.com 2010-09-29 12:33 EDT------- (In reply to comment #18) > The problem can be resolved with options --disable --device sit0 when doing > network test. change the severity to high as 'disable' sit0 works Can the test suite beta (v7-1.3-19) be tested to verify this issue is resolved? ------- Comment From hienn.com 2011-03-28 11:46 EDT------- Working on the test, will post the results when done.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
In v7 1.2, a problem has been observed that network test included sit0 interface which is not necessarily required for testing. This issue has been fixed in v7 1.3, now sit0 interface is no longer planned nor executed during network testing.
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 therefore 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. http://rhn.redhat.com/errata/RHBA-2011-0497.html |