Red Hat Bugzilla – Bug 1008377
rhev-h auto install failed during create_hostvg for iscsi boot
Last modified: 2014-05-06 03:21:37 EDT
Created attachment 798196 [details]
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
< "primary ext2 " + str(self.ROOT_SIZE * 2) +
< " -1\"")
> "primary ext2 512M -1\"")
Version-Release number of selected component (if applicable):
Steps to Reproduce:
no this issue in rhev-h 6.4.z, so it's a regression bug.
Could reproduce "rhev-h auto install failed during create_hostvg for iscsi boot"
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?
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.
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
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.
According to Comment 10, verified 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:
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.