Bug 790332 - kickstart: "network --device link" doesn't work
Summary: kickstart: "network --device link" doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-14 09:45 UTC by Kamil Páral
Modified: 2012-02-29 15:42 UTC (History)
5 users (show)

Fixed In Version: anaconda-17.10-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-29 15:42:52 UTC
Type: ---


Attachments (Terms of Use)

Description Kamil Páral 2012-02-14 09:45:28 UTC
Description of problem:
http://fedoraproject.org/wiki/Anaconda/Kickstart#network says for "--device" option:

"Specifies device to be configured and/or activated with the network command. The device can be specified in the same ways as ksdevice boot option."

Looking at http://fedoraproject.org/wiki/Anaconda/Options#ksdevice option:

"Takes one of 4 types of argument which tells install what network device to use for kickstart from network:
The keyword 'link' indicating that the first interface with link up"

But if I put this command in my kickstart:

network --device link

Anaconda ends with an error: "The provided network interface link does not exist"

Either the documentation is wrong or the code is wrong.

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

How reproducible:
always

Comment 1 Radek Vykydal 2012-02-14 13:01:40 UTC
These update images should fix it, sending patch for support of --device=link in stage 2 kickstart to anaconda-devel-list.

http://rvykydal.fedorapeople.org/updates.link.img
http://rvykydal.fedorapeople.org/updates.link.img.iso

Comment 2 Kamil Páral 2012-02-14 13:28:44 UTC
Yes, that updates.img fixes the issue. Thanks.

Comment 3 Radek Vykydal 2012-02-17 08:25:43 UTC
This should be fixed in anaconda-17.10-1

Comment 4 Kamil Páral 2012-02-29 15:42:52 UTC
Confirmed fixed in anaconda 17.11


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