This test scenario make sure that {{filename|ksdevice=<interface name>}} format will handle interface names of the form {{filename|emN or pci<slot>#<port>}}. For example

+

{{QA/Test_Case

−

passing 'ksdevice=em1' will work without issues.

+

|description=This test scenario make sure that <code>ksdevice=<iface></code> format will handle interface names of the form <code>emN</code> and <code>pci<slot>#<port></code>. For example passing <code>ksdevice=em1</code> will work without issues.

# Download, or [[How_to_build_a_Rawhide_ISO_image_for_testing|create]], installation media (either a {{filename|boot.iso}}, PXE images or a {{filename|DVD.iso}}). If participating during the [[Test_Day:2011-01-27_Network_Device_Naming_With_Biosdevname|biosdevname test day]], a {{filename|boot.iso}} will be provided on the test day wiki page.

+

|actions=

+

<ol>

+

<li> Create a kickstart file to automate a Fedora installation. The quickest method is to copy the kickstart file {{filename|/root/anaconda-ks.cfg}} that describes the installation for the existing system. Adjust the kickstart file to ensure the <code>network</code> keyword specifies the configuration parameters for the network interfaces using the new naming convention. For example, to configure three devices you might use the kickstart sample below. More information on kickstart options, and creating a kickstart file can be found at [[Anaconda/Kickstart]].

Once completed, upload the kickstart file to a network location accessible to your system under test. You can [[Special:Upload|upload your file to the Fedora wiki]], a pastebin.com (or similar) service, or another system on your local network.

+

<li> Initiate a {{FedoraVersion|long|next}} (or [[Releases/Rawhide|Rawhide]]) installation by booting the installer using any available method (e.g. {{filename|boot.iso}}, PXE images or {{filename|DVD.iso}}).

+

<li> At the bootloader screen, press <code>Tab</code> to edit the boot arguments and append <code>ksdevice=em1 ks=http://server/path/to/ks.cfg</code>. Specify the correct <code>ks=</code> parameter that you chose in ''step#1''.

+

<li> Complete the installation, login to the system.

+

</ol>

−

== Setup ==

+

|results=

−

== Actions ==

+

<ol>

−

== Results ==

+

<li> Make sure {{filename|ks.cfg}} is retrieved over the network through the interface specified with <code>ksdevice</code> option. Manual inspection of {{filename|/var/log/anaconda.log}} may be required.

<li> Once you login to the system, make sure that onboard device names are of the form <code>emN</code> as described [[QA:Testcase biosdevname on-board network interface names|here]]. You can inspect the contents of {{filename|/sys/class/net/}} to ensure device names are named properly, for example:

+

<pre># ls /sys/class/net/

+

em1 em2 em3 em4 lo</pre>

+

<li> Make sure that PCI add-in device names are of the form <code>pci<slot>#<port></code>. As described [[QA:Testcase biosdevname add-in network interface names|here]]. You can inspect the contents of {{filename|/sys/class/net/}} to ensure device names are named properly, for example:

+

<pre># ls /sys/class/net/

+

lo pci3#1 pci3#2 pci4#1</pre>

+

<li> Make sure the configuration parameters specified in the kickstart file are applied to the specified interfaces. For example, if you specified a device named <code>em1</code> to be setup to boot automatically using DHCP, verify using the {{command|ifconfig}} command as shown below

+

<pre># ifconfig em1

+

em1 Link encap:Ethernet HWaddr 00:24:E8:2E:DE:FF

+

inet addr:172.16.65.55 Bcast:172.16.127.255 Mask:255.255.192.0

+

inet6 addr: fe80::224:e8ff:fe2e:deff/64 Scope:Link

+

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

+

RX packets:778483 errors:0 dropped:0 overruns:0 frame:0

+

TX packets:95453 errors:0 dropped:0 overruns:0 carrier:0

+

collisions:0 txqueuelen:1000

+

RX bytes:133048578 (126.8 MiB) TX bytes:25692991 (24.5 MiB)

+

Interrupt:36 Memory:d6000000-d6012800</pre>

+

<li> Make sure {{filename|ifcfg-emN}} and {{filename|ifcfg-pci<slot>#<port>}} files are created under the dir {{filename|/etc/sysconfig/network-scripts}} after the installation is complete.

Setup

Download, or create, installation media (either a boot.iso, PXE images or a DVD.iso). If participating during the biosdevname test day, a boot.iso will be provided on the test day wiki page.

How to test

Create a kickstart file to automate a Fedora installation. The quickest method is to copy the kickstart file /root/anaconda-ks.cfg that describes the installation for the existing system. Adjust the kickstart file to ensure the network keyword specifies the configuration parameters for the network interfaces using the new naming convention. For example, to configure three devices you might use the kickstart sample below. More information on kickstart options, and creating a kickstart file can be found at Anaconda/Kickstart.

Once completed, upload the kickstart file to a network location accessible to your system under test. You can upload your file to the Fedora wiki, a pastebin.com (or similar) service, or another system on your local network.

Initiate a Fedora 22 (or Rawhide) installation by booting the installer using any available method (e.g. boot.iso, PXE images or DVD.iso).

At the bootloader screen, press Tab to edit the boot arguments and append ksdevice=em1 ks=http://server/path/to/ks.cfg. Specify the correct ks= parameter that you chose in step#1.

Complete the installation, login to the system.

Expected Results

Make sure ks.cfg is retrieved over the network through the interface specified with ksdevice option. Manual inspection of /var/log/anaconda.log may be required.

Make sure kickstart installation proceeds without any manual intervention required.

Once you login to the system, make sure that onboard device names are of the form emN as described here. You can inspect the contents of /sys/class/net/ to ensure device names are named properly, for example:

# ls /sys/class/net/
em1 em2 em3 em4 lo

Make sure that PCI add-in device names are of the form pci<slot>#<port>. As described here. You can inspect the contents of /sys/class/net/ to ensure device names are named properly, for example:

# ls /sys/class/net/
lo pci3#1 pci3#2 pci4#1

Make sure the configuration parameters specified in the kickstart file are applied to the specified interfaces. For example, if you specified a device named em1 to be setup to boot automatically using DHCP, verify using the ifconfig command as shown below