Bug 675118

Summary: /pre-trigger/30parse-biosdevname.sh: 10: [[: not found
Product: Red Hat Enterprise Linux 6 Reporter: Alexander Todorov <atodorov>
Component: dracutAssignee: Harald Hoyer <harald>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: jburke, ksrot, pknirsch, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dracut-004-41.el6 Doc Type: Bug Fix
Doc Text:
This bug only happened in the development phase of this package, and did not happen in a released package.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 11:54:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 501533, 670159    

Description Alexander Todorov 2011-02-04 11:24:41 UTC
Description of problem:
When booting a KVM domU with one of the latest nightly builds in single user mode I get the error message:
/pre-trigger/30parse-biosdevname.sh: 10: [[: not found
   Welcome to Red Hat Enterprise Linux Workstation 

Version-Release number of selected component (if applicable):
dracut-004-36.el6

How reproducible:
always

Steps to Reproduce:
1. Install KVM domU with Workstation variant, default package set
2. After reboot append "1" to grub command line to boot into single user mode
3. cat /var/log/boot.log | head 
  
Actual results:
/pre-trigger/30parse-biosdevname.sh: 10: [[: not found
   Welcome to Red Hat Enterprise Linux Workstation 


Expected results:
No errors in the script. 

Additional info:

Comment 2 Harald Hoyer 2011-02-08 11:52:27 UTC
Despite the error message everything else regarding biosdevname should work.

Comment 4 Harald Hoyer 2011-02-16 11:31:40 UTC
    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:
This bug only happened in the development phase of this package, and did not happen in a released package.

Comment 5 Alexander Todorov 2011-02-17 14:22:49 UTC
With dracut-004-39.el6.noarch I got:

NMI watchdog disabled for cpu0: unable to create perf event: -2
[: 10: !=: unexpected operator
    Welcome to Red Hat Enterprise Linux Workstation 

Not sure if this is related or it's completely different error.

Comment 6 Alexander Todorov 2011-02-17 14:35:31 UTC
I have biosdevname installed on the system. When booting with:

biosdevname=1 - no error is printed
biosdevname=0 - [: 10: !=: unexpected operator

Don't specify biosdevname parameter, same error.

Comment 7 Harald Hoyer 2011-02-25 08:40:53 UTC
*** Bug 680262 has been marked as a duplicate of this bug. ***

Comment 9 Karel Srot 2011-03-03 11:24:45 UTC
*** Bug 681818 has been marked as a duplicate of this bug. ***

Comment 10 Karel Srot 2011-03-03 11:26:16 UTC
dracut-004-39.el6.noarch:

During the system boot following message appears in the console:
 1: !=: unexpected operator

Seems like USE_BIOSDEVNAME in parse-biosdevname.sh is not properly initialized.

Below is a fragment of dmesg:

dracut: + [ -e /pre-trigger/30parse-biosdevname.sh ]
dracut: + . /pre-trigger/30parse-biosdevname.sh
dracut: + getarg biosdevname
dracut: + set +x
dracut: + return 1
dracut: biosdevname=1: activating biosdevname network renaming
dracut: + USE_BIOSDEVNAME=
dracut: + [ != 1 ]
dracut: [: 1: !=: unexpected operator
dracut: + info biosdevname=1: activating biosdevname network renaming
dracut: + check_quiet
dracut: + [ -z yes ]
dracut: + echo <6>dracut: biosdevname=1: activating biosdevname network
renaming
dracut: + [ yes != yes ]
dracut: + udevproperty UDEV_BIOSDEVNAME=1

Comment 11 Harald Hoyer 2011-03-03 11:55:55 UTC
See "Fixed In Version: dracut-004-41.el6"

Comment 14 Alexander Todorov 2011-03-09 13:07:28 UTC
I no longer see this error with dracut-004-43.el6.noarch.

Comment 15 errata-xmlrpc 2011-05-19 11:54:16 UTC
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-0523.html