Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #922593 +++
Description of problem:
When I install automatically the ovirt-node-2.6.1 iso that I built based on rhel6.3 repo to our machine via pxe, I ran into the following error:
Starting ovirt-firstboot: Performing automatic disk partitioning
ERROR:ovirtnode.storage:HostVG/AppVG exists on a separate disk
ERROR:ovirtnode.storage:Manual Intervention required
It seems the auto install will stop if the "HostVG" exists on the
disk on the machine.
In the emergency shell
[root@mcptest ~]# cat /proc/cmdline
ksdevice=bootif text BOOTIF=eth0 firstboot storage_init=/dev/sda lang= storage_vol=50:1024:512:5:2048:-1 standalone hostname=mcptest
vga=791 rootpw=$1$cfm5kMmj$M1uknfs/8aSeZkJyf/NBC/
root=live:/ovirt-node-image-2.6.1-1.1.el6.iso ssh_pwauth=1
ks=http://9.181.129.219/cblr/svc/op/ks/system/62 rootfstype=auto ro
liveimg nomodeset check rootflags=loop crashkernel=512M-2G:64M,2G-:128M
elevator=deadline processor.max_cstate=1 install rhgb rd_NO_LUKS
rd_NO_MD rd_NO_DM
[root@mcptest ~]# pvs
PV VG Fmt Attr
PSize PFree
/dev/mapper/3600605b003b86620166a1ddb0bfa15b7p4 HostVG lvm2 a--
1.36t 0
We are installing it to the hard disk , and the previous installation is
RHEVH 6.3. During the installation, before performing the disk format, it checks that there is a existing HostVG on the disk, so it stops installing.
There is another question confused me. If I install rhev-hypervisor6-6.4-20130221 with ovirt-node-2.5.0 via pxe, which has same check_existing_hostvg code as what mentioned below, I can install it successfully, in addition, I do some debug before run
_functions.OVIRT_VARS["OVIRT_ROOT_INSTALL"] = "y"
if _functions.check_existing_hostvg("") or \
_functions.check_existing_hostvg("","AppVG"):
logger.error("HostVG/AppVG exists on a separate disk")
logger.error("Manual Intervention required")
return False
if storage.perform_partitioning():
return True
[root@mcptest ~]# pvs
I didn't got the HostVG information that got in ovirt-node-2.6.1 version. So I guess ovirt-node-2.5.0 does something about HostVG before check
but ovirt-node-2.6.1 doesn't.
Version-Release number of selected component (if applicable):
2.6.1
How reproducible:
Steps to Reproduce:
1. Build an ovirt-node-2.6.1 iso based on rhel6.3 repo
2. Install the iso to a bare mahcine via pxe, the parameters is like below:
sdevice=bootif text BOOTIF=eth0 firstboot storage_init=/dev/sda lang= storage_vol=50:1024:512:5:2048:-1 standalone hostname=mcptest
vga=791 rootpw=$1$cfm5kMmj$M1uknfs/8aSeZkJyf/NBC/
root=live:/ovirt-node-image-2.6.1-1.1.el6.iso ssh_pwauth=1
ks=http://9.181.129.219/cblr/svc/op/ks/system/62 rootfstype=auto ro
liveimg nomodeset check rootflags=loop crashkernel=512M-2G:64M,2G-:128M
elevator=deadline processor.max_cstate=1 install rhgb rd_NO_LUKS
rd_NO_MD rd_NO_DM
3.
Actual results:
Starting ovirt-firstboot: Performing automatic disk partitioning
ERROR:ovirtnode.storage:HostVG/AppVG exists on a separate disk
ERROR:ovirtnode.storage:Manual Intervention required
Expected results:
Get installed successfully
Additional info:
RHEV-H QE can reproduce this issue.
Seems it is related to ovirt-node-2.6.1 but no rhel6.3 repo, because I can reproduce this issue with rhel6.4 repo.
Test steps:
1. Build an ovirt-node-2.6.1 iso based on rhel6.4 repo.
2. Make profile with above iso.
3. Auto install RHEV-H via PXE with below parameters:
BOOTIF=XX storage_init=/dev/sda storage_vol=::::: adminpw=XXX firstboot
Test result:
Automatic installation failed.
Starting ovirt-firstboot: Performing automatic disk partitioning
ERROR:ovirtnode.storage:HostVG/AppVG exists on a separate disk
ERROR:ovirtnode.storage:Manual Intervention required
Fix appears to be in adding back the install/check files for dracut since RHEL based dracut is the older version. ovirt-cleanup modules are left out of the initrd and are not cleaning up the HostVG group on boot. 6.4 version of ovirt-node has that specific patch already will need to put back in.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes
Thanks in advance.
Test version:
rhevh-6.5-20131031.1.0
ovirt-node-3.0.1-7.el6.noarch
According comment 1 & 2, it is ovirt-node issue, so my test steps as following:
1. Boot from PXE, auto install RHEV-H with below parameters:
BOOTIF=XX storage_init=/dev/sda storage_vol=::::: adminpw=XXX firstboot
Test result:
The auto install is succeed.
So the bug is fixed, change bug status is VERIFIED.
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/RHBA-2014-0033.html