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.
Created attachment 798196[details]
attached Screenshot
Description of problem:
RHEV-H auto install failed during create_hostvg for iscsi boot with the follow parameter:
BOOTIF=eth0 storage_init=/dev/vda,/dev/sda iscsi_init=/dev/sda iscsi_target_name=iqn.2013-01.com:hadong iscsi_install iscsi_server=10.66.11.127:3260 firstboot
it auto install failed with follow infoseen ovirt-node.log.png)
parted "/dev/mapper/1IET_00010001" -s "mkpart primary ext2 512M -1"
Error:You requested a partition from 512MB to 32.2GB
The closest location we can manage is 1024MB to 32.2GB
Maybe change the follow code can resole this issue.
[root@agent2 ovirtnode]# diff storage.py storage.py.backup
436,437c436
< "primary ext2 " + str(self.ROOT_SIZE * 2) +
< " -1\"")
---
> "primary ext2 512M -1\"")
Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.625.el6.iso
How reproducible:
100%
Steps to Reproduce:
Actual results:
Expected results:
Additional info:
no this issue in rhev-h 6.4.z, so it's a regression bug.
Test version:
rhev-hypervisor6-6.5-20130916.0.el6ev.iso
ovirt-node-3.0.1-1.el6
Could reproduce "rhev-h auto install failed during create_hostvg for iscsi boot"
issue.
Hey, jboggs,
My patch:
http://gerrit.ovirt.org/#/c/19271/
just fixed the create_hostvg issue during rhev-h auto install.
i'll meet another issue for iscsi boot during rhev-h auto install. I add "TestBlocker" into "Keywords" because "iscsi boot" is an important feature for rhev-h 6.5.
Could you look at this bug?
Test version:
rhev-hypervisor6-6.5-20130930.0.auto665.el6.iso
ovirt-node-3.0.1-3.el6.noarch
This bug has been fixed by above auto jenkins build. rhev-h auto install success for iscsi boot.Also boot it and login rhev-h success.
I am waiting office build to verify this bug.
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6
Test steps:
BOOTIF=eth0 storage_init=/dev/sda,/dev/sdb iscsi_init=/dev/sdb iscsi_target_name=iqn.2013-01.com:hadong iscsi_install iscsi_server=10.66.11.127:3260 firstboot
Test results:
rhev-h auto install success for iscsi boot.Also boot it and login rhev-h success.
so this bug has been fixed.
After this status of bug changed from "MODIFIED" to "ON_QA", i will verify this bug.
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.
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