Hide Forgot
This bug has been copied from bug #667434 and has been proposed to be backported to 5.6 z-stream (EUS).
Created attachment 473935 [details] Patch
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: If a user passed in the "single" kernel command line argument to boot the node in single user mode, the argument captured and stored and used each time the hypervisor was booted. Now, rhev-h will detect the "single" argument and will not store it. It will only be used for the time that it specified, and not for all future boots.
Verified on 5.6-9.1, bug is fixed. Verify steps: 1. Boot into single user mode. 2. "Single" kernel boot argument isn't stored in /etc/default/ovirt 3. Reboot, no "single" kernel boot argument pass to kernel line and boot normally.
According to comment 6, change the status to 'Verified'.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -If a user passed in the "single" kernel command line argument to boot the node in single user mode, the argument captured and stored and used each time the hypervisor was booted. Now, rhev-h will detect the "single" argument and will not store it. It will only be used for the time that it specified, and not for all future boots.+Prior to this update, when the "single" kernel boot option was used to boot a node in single user mode, Red Hat Enterprise Virtualization Hypervisor added this option to the /etc/default/ovirt configuration file. However, this caused such node to enter single user mode every time it was booted. With this update, this error has been fixed, and Red Hat Enterprise Virtualization Hyperviser no longer adds the "single" kernel boot option to the /etc/default/ovirt file.
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-0352.html