[Users] proliant errors trying to install ovirt-node image

[Joe Pruett]

On 03/05/2012 07:00 AM, Joey Boggs wrote:
> On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote:
>>> -----Original Message-----
>>> From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On
>>> Behalf Of ext Joe Pruett
>>> Sent: Sunday, March 04, 2012 2:11 AM
>>> To: users at ovirt.org
>>> Subject: [Users] proliant errors trying to install ovirt-node image
>>>
>>> i've already found the info on the list about the "global name 'disk'
>>> not defined" error and i've tried both an iso from the jenkins url
>>> listed, as well as creating my own git area using the 2.2.3 tagged code
>>> and making the one line change to fix that python error.  but neither
>>> of
>>> those images work either.   i get a generic "ovirt node hypervisor
>>> installation failed" message.  i've poked around the log viewers and at
>>> the end i see it complaining that the gpt partition label has no bios
>>> bootable partition, but it isn't clear if that is really the issue.
>> I ran into the same problems as you when trying to install on a
>> HP ProLiant BL460c G1 blade.
>>
>> The Red Hat Bugzilla report #798030 "TUI Installation fails with
>>  Grub error" seems to address exactly this kind of problem.
>>
>> The grub2-setup complaining has got its reason: In file script/storage.py
>> the disk partitioning is done using a GPT, but no partition with 
>> flag bios_grub is created.
>>
>> I modified the source (mis-)using the first partition (EFI partition)
>> in case of a non-EFI boot as a bios_grub flagged partition. This
>> partition is much bigger than necessary (grub2.info recommends one
>> or two MB), thus leaving some room for optimization for the experts when
>> fixing the problem.
>>
>> Please find the patch that allowed successful installation in the
>> attachment.
> Can you submit this through gerrit, its looks fine to me and I don't
> see any problem merging it.
> http://ovirt.org/wiki/Working_with_gerrit.ovirt.org

i'll be testing this later and will give feedback.

>>> i'm
>>> wondering if there might be more cciss driver issues.
>>>
>>> i haven't dug into the source to figure out the root pw so i could more
>>> easily look at the log files or export them.  can someone enlighten me
>>> with that more quickly than i can find it?
>> As I am stuck to reading log files online or exporting them via screen shots,
>> I am also interested in learning about better ways of exporting. 
> The root password isn't set by default, you can however press F2
> inside the installer or the configuration menus  to get to a shell
> prompt and setup networking to get logs off there.

i discovered that the root pw is explicitly locked.  f2 does nothing at
the error screen, alt-f2 shows a login prompt.  does f2 stop working at
some point during the process?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20120305/ec4d5bd4/attachment-0001.html>