RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 675118 - /pre-trigger/30parse-biosdevname.sh: 10: [[: not found
Summary: /pre-trigger/30parse-biosdevname.sh: 10: [[: not found
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dracut
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Harald Hoyer
QA Contact: Release Test Team
URL:
Whiteboard:
: 680262 681818 (view as bug list)
Depends On:
Blocks: 501533 670159
TreeView+ depends on / blocked
 
Reported: 2011-02-04 11:24 UTC by Alexander Todorov
Modified: 2011-05-19 11:54 UTC (History)
4 users (show)

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.
Clone Of:
Environment:
Last Closed: 2011-05-19 11:54:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0523 0 normal SHIPPED_LIVE dracut bug fix and enhancement update 2011-05-18 17:44:57 UTC

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
Note You need to log in before you can comment on or make changes to this bug.