Description of problem: The following patch adds layer2 support to Anaconda Version-Release number of selected component (if applicable): RHEL 5.0 How reproducible: Define layer2 VSWITCH, couple NIC Actual results: qeth hardware error when brought online Additional info: Requires LAYER2=1 to be added to CONF file
Created attachment 150630 [details] Patch to set layer2 mode if LAYER2=1 is defined
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Created attachment 150706 [details] Better patch, adds prompt in interactive mode
Created attachment 151218 [details] Test initrd based on RHEL 5 GA
*** Bug 184669 has been marked as a duplicate of this bug. ***
Created attachment 152002 [details] Full support for layer2/layer3 - Support for LAYER2=0 or LAYER2=1 in CONF file - Support for interactive LPAR install - Corresponding option added to initscript automatically -- ARP=no for layer 3 -- OPTIONS="layer2=1" for layer 2
Created attachment 152004 [details] Test files based on RHEL 5.0 To test, untar to root of install tree. File contains: images/initrd.img : updated initrd RHupdates/network.py : updated python script
This enhancement request was evaluated by the full Red Hat Enterprise Linux team for inclusion in a Red Hat Enterprise Linux minor release. As a result of this evaluation, Red Hat has tentatively approved inclusion of this feature in the next Red Hat Enterprise Linux Update minor release. While it is a goal to include this enhancement in the next minor release of Red Hat Enterprise Linux, the enhancement is not yet committed for inclusion in the next minor release pending the next phase of actual code integration and successful Red Hat and partner testing.
For release note: --- The following applies to the s390x architecture only. Anaconda now supports connections to a VSWITCH, GuestLAN or OSA in layer 2 mode. The installer will now prompt for the mode in the initial stage of the installation. The value provided for the mode also affects the resulting network interface startup script after installation. For layer 2 installations, the value OPTIONS="layer2=1" is written to ifcfg-eth0; for layer 3, the value ARP=no is written. Please note that when installing under z/VM, you can add either LAYER2=0 or LAYER2=1 to the CMS CONF file to avoid being prompted for the mode each time. Use LAYER2=0 when the OSA is in layer 3 mode, and LAYER2=1 when the OSA is in layer 2 mode.
adding to Release Notes (appearing after Beta): <quote> (s390x) Anaconda now supports connections to a VSWITCH, GuestLAN, or OSA in layer 2 mode. The installer will now prompt for the mode in the initial stage of the installation. The value provided for the mode also affects the resulting network interface startup script after installation. For layer 2 installations, the value OPTIONS="layer2=1" is written to ifcfg-eth0; for layer 3, the value ARP=no is written. Note that when installing on a Series z machine or guest, you can add either LAYER2=0 or LAYER2=1 to the CMS CONF file to avoid being prompted for the mode each time. Use LAYER2=0 when the OSA is in layer 3 mode, and LAYER2=1 when the OSA is in layer 2 mode. </quote> please advise if any revisions are necessary. thanks!
*** Bug 245588 has been marked as a duplicate of this bug. ***
Based on bug 248049, can we edit the last paragraph to say this: --- Note that when installing on a System z guest, you can add either LAYER2=0 or LAYER2=1 to the CMS CONF file to avoid being prompted for the mode each time. Use LAYER2=0 when the OSA is in layer 3 mode, and LAYER2=1 when the OSA is in layer 2 mode. When specifying LAYER2=1, you can also specify VSWITCH=1 when connecting to a VSWITCH, or VSWITCH=0 when attaching the OSA directly. When a VSWITCH is not in use, you must specify the MAC address, or specify this in the CMS CONF file beginning with MACADDR=. When using a VSWITCH, this value is not necessary as it is provided automatically.
thanks Brad, edited the note as follows: <quote> Note that when installing on a System z guest, you can make the mode persistent. To do so, add either LAYER2=0 or LAYER2=1 to the CMS CONF file. Use LAYER2=0 when the OSA is in layer 3 mode, and LAYER2=1 when the OSA is in layer 2 mode. When specifying LAYER2=1, you can also specify VSWITCH=1 when connecting to a VSWITCH, or VSWITCH=0 when connecting directly to the OSA. If a VSWITCH is not in use, specify the MAC address in the CMS CONF file using the parameter MACADDR=<MAC address>. </quote> please advise if any further revisions are required. note that the release notes deadline is on 16 August (Thursday), at which point it'll be locked and dropped for Translation. thanks!
Update: This release note change is dependent on bug 248049 getting approved (waiting on PM). Looking into that now (before Thursday deadline).
A fix for this issue has been included in the packages contained in the beta (RHN channel) or most recent snapshot (partners.redhat.com) for RHEL5.1. Please verify that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED.
Brad, revising the release note to change "CMS CONF" to "CMS configuration file". FYI
A fix for this issue should have been included in the packages contained in the most recent snapshot (partners.redhat.com) for RHEL5.1. Requested action: Please verify that your issue is fixed as soon as possible to ensure that it is included in this update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. More assistance: If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
A fix for this issue should have been included in the packages contained in the RHEL5.1-Snapshot4 on partners.redhat.com. Requested action: Please verify that your issue is fixed *as soon as possible* to ensure that it is included in this update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
A fix for this issue should have been included in the packages contained in the RHEL5.1-Snapshot6 on partners.redhat.com. Requested action: Please verify that your issue is fixed ASAP to confirm that it will be included in this update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
A fix for this issue should have been included in the packages contained in the RHEL5.1-Snapshot7 on partners.redhat.com. Requested action: Please verify that your issue is fixed ASAP to confirm that it will be included in this update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
IBM: Can you confirm that the reported defect is no longer present in snapshot#7?
A fix for this issue should be included in the packages contained in RHEL5.1-Snapshot8--available now on partners.redhat.com. IMPORTANT: This is the last opportunity to confirm that your issue is fixed in the RHEL5.1 update release. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to FAILS_QA. If you cannot access bugzilla, please reply with a message to Issue Tracker and I will change the status for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager.
The layer 2 support got verified on IBM site. For details please refer to: LTC 21811 - RIT88406- FEAT:200121: update s390 init scripts to support OSA layer 2 and CDLC NICs Seems this is the Anaconda part for that. If so then its als overified OK
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. http://rhn.redhat.com/errata/RHBA-2007-0644.html