Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 740576

Summary: anaconda writes wrong device to root= parameter
Product: [Fedora] Fedora Reporter: Dan Horák <dan>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-17.2-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 788669 (view as bug list) Environment:
Last Closed: 2012-02-08 19:22:15 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:
Bug Depends On:    
Bug Blocks: 467765, 718271, 788669    
Attachments:
Description Flags
use device name for the root= parameter none

Description Dan Horák 2011-09-22 14:21:21 UTC
Created attachment 524420 [details]
use device name for the root= parameter

anaconda writes wrong device (in fact it's path to kernel image) instead of the device where root filesystem resides


Version-Release number of selected component (if applicable):
anaconda-16.18-1.fc16
  
Actual results:
root=/boot/vmlinuz-3.1.0-0.rc6.git0.0.fc16.s390x

Expected results:
root=/dev/mapper/vg_devel4-lv_root

Comment 1 David Lehman 2011-11-04 20:26:29 UTC
David, I happened to write a patch for this when it first came in, but I never took the bug. I realized today, after posting the patch for review, that it's assigned to you. Surely you don't mind one less s390 bug.

Comment 2 David Lehman 2012-02-08 19:22:15 UTC
This was fixed in anaconda-17.2-1.