Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 788225 - autoinstall fails when local_boot or upgrade not passed on command line
autoinstall fails when local_boot or upgrade not passed on command line
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
6.3
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Mike Burns
Virtualization Bugs
: ZStream
Depends On: 788179
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-07 14:27 EST by Chris Pelland
Modified: 2016-04-26 09:59 EDT (History)
11 users (show)

See Also:
Fixed In Version: ovirt-node-2.0.2-0.14.3.git3eac501.el6_2.5
Doc Type: Bug Fix
Doc Text:
Previously, autoinstall would fail if the firstboot or reinstall options were passed but local_boot or upgrade were not passed. Now, neither the local_boot or upgrade parameters are required for autoinstall.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-15 11:10:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0109 normal SHIPPED_LIVE Important: rhev-hypervisor6 security and bug fix update 2012-02-15 16:09:24 EST

  None (edit)
Description Chris Pelland 2012-02-07 14:27:30 EST
This bug has been copied from bug #788179 and has been proposed
to be backported to 6.2 z-stream (EUS).
Comment 5 Guohua Ouyang 2012-02-07 22:23:49 EST
verified on 6.2-20120207.0:
autoinstall with local_boot/update + iscsi_name is successful.
Comment 6 Mike Burns 2012-02-08 07:52:10 EST
(In reply to comment #5)
> verified on 6.2-20120207.0:
> autoinstall with local_boot/update + iscsi_name is successful.

The test needs to be autoinstall with firstboot/reinstall + storage_init + BOOTIF.  That combination would result in it auto-installing, but then starting the TUI and reporting an invalid installation.
Comment 7 Guohua Ouyang 2012-02-08 21:47:46 EST
(In reply to comment #6)
> (In reply to comment #5)
> > verified on 6.2-20120207.0:
> > autoinstall with local_boot/update + iscsi_name is successful.
> 
> The test needs to be autoinstall with firstboot/reinstall + storage_init +
> BOOTIF.  That combination would result in it auto-installing, but then starting
> the TUI and reporting an invalid installation.

retested, do autoinstall with BOOTIF + storage_init + firstboot/reinstall is successful, did not see ""Invalid installation, please reboot with
reinstall".  

keep bug's status be "verified".
Comment 8 Mike Burns 2012-02-10 11:28:46 EST
    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:
Previously, autoinstall would fail if the firstboot or reinstall options were passed but local_boot or upgrade were not passed.  Now, local_boot/upgrade are not required for autoinstall.
Comment 9 Stephen Gordon 2012-02-10 11:37:52 EST
    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 @@
-Previously, autoinstall would fail if the firstboot or reinstall options were passed but local_boot or upgrade were not passed.  Now, local_boot/upgrade are not required for autoinstall.+Previously, autoinstall would fail if the firstboot or reinstall options were passed but local_boot or upgrade were not passed.  Now, neither the local_boot or upgrade parameters are required for autoinstall.
Comment 10 errata-xmlrpc 2012-02-15 11:10:29 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0109.html

Note You need to log in before you can comment on or make changes to this bug.