Red Hat Bugzilla – Bug 500198
Anaconda /proc/cmdline parsing during the installation is broken.
Last modified: 2011-07-21 02:52:11 EDT
Description of problem: Anaconda /proc/cmdline parsing during the installation is broken. Version-Release number of selected component (if applicable): anaconda-11.1.2.168 How reproducible: always Steps to Reproduce: 1. Boot the installation media (boot.iso, virt-install kernel+initrd.img, install DVD) 2. Add some parameters at the boot: prompt line, use quotation marks (for example: ethtool="speed 100 duplex full autoneg off" 3. Continue the installation 4. Anaconda gets the stage2 and tracebacks Actual results: shlex.py booms with ValueError: "No closing quotation" Expected results: Installation without a problem. Additional info: Probably related to the bug 453212. The code in flags.py is just wrong. It may solve pxe case, but it breaks other booting methods (see the lines 40-41): 33 def createCmdlineDict(self): 34 cmdlineDict = {} 35 cmdline = open("/proc/cmdline", "r").read().strip() 36 37 # if the BOOT_IMAGE contains a space, pxelinux will strip one of the 38 # quotes leaving one at the end that shlex doesn't know what to do 39 # with 40 if cmdline.find("BOOT_IMAGE=") and cmdline.endswith('"'): 41 cmdline = cmdline.replace("BOOT_IMAGE=", "BOOT_IMAGE=\"") 42 43 lst = shlex.split(cmdline) 44
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
qa_ack+ please?
Tested and verified with 0430.2 build. Booted from DVD with: linux ethtool="speed 100 duplex full autoneg off" There was no traceback.
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-0984.html