-----Original Message----- From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of ext Joe Pruett Sent: Sunday, March 04, 2012 2:11 AM To: users@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'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
This is a multi-part message in MIME format. --------------050903050303010609070402 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote: the installer or the configuration menus to get to a shell prompt and setup networking to get logs off there.
what is the best procedure to follow to try and get to the bottom of issues like this? might i be better off installing a regular os and then installing the vdsm package? Installing Fedora 16 on the same kind of blade worked for me without any problems. Therefore the "regular os + vdsm rpms" approach could help you to sidestep the failing ovirt-node installation, but it will probably not help you in analyzing and fixing ovirt-node related installation issues.
Best regards,
Hermann Huy
St.-Martin-Str. 76 81541 München Tel: +49 89 5159 35744 Mob: +49 170 5630316 Email: hermann.huy@nsn.com http://www.nokiasiemensnetworks.com/global/
Nokia Siemens Networks GmbH& Co. KG Sitz der Gesellschaft: München / Registered office: Munich Registergericht: München / Commercial registry: Munich, HRA 88537 WEEE-Reg.-Nr.: DE 52984304
Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management GmbH Geschäftsleitung / Board of Directors: Hermann Rodler, Olaf Horsthemke Vorsitzender des Aufsichtsrats / Chairman of supervisory board: Herbert Merz Sitz der Gesellschaft: München / Registered office: Munich Registergericht: München / Commercial registry: Munich, HRB 163416
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------050903050303010609070402 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote: <blockquote cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">-----Original Message----- From: <a class="moz-txt-link-abbreviated" href="mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a> [<a class="moz-txt-link-freetext" href="mailto:users-bounces@ovirt.org">mailto:users-bounces@ovirt.org</a>] On Behalf Of ext Joe Pruett Sent: Sunday, March 04, 2012 2:11 AM To: <a class="moz-txt-link-abbreviated" href="mailto:users@ovirt.org">users@ovirt.org</a> 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. </pre> </blockquote> <pre wrap="">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. </pre> </blockquote> Can you submit this through gerrit, its looks fine to me and I don't see any problem merging it.<br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://ovirt.org/wiki/Working_with_gerrit.ovirt.org">http://ovirt.org/wiki/Working_with_gerrit.ovirt.org</a><br> <blockquote cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">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? </pre> </blockquote> <pre wrap="">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. </pre> </blockquote> 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.<br> <blockquote cite="mid:DCD6CDDD48B20D47807322CD835D26E0011837D4@DEMUEXC013.nsn-intra.net" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap=""> what is the best procedure to follow to try and get to the bottom of issues like this? might i be better off installing a regular os and then installing the vdsm package? </pre> </blockquote> <pre wrap="">Installing Fedora 16 on the same kind of blade worked for me without any problems. Therefore the "regular os + vdsm rpms" approach could help you to sidestep the failing ovirt-node installation, but it will probably not help you in analyzing and fixing ovirt-node related installation issues. Best regards, Hermann Huy St.-Martin-Str. 76 81541 München Tel: +49 89 5159 35744 Mob: +49 170 5630316 Email: <a class="moz-txt-link-abbreviated" href="mailto:hermann.huy@nsn.com">hermann.huy@nsn.com</a> <a class="moz-txt-link-freetext" href="http://www.nokiasiemensnetworks.com/global/">http://www.nokiasiemensnetworks.com/global/</a> Nokia Siemens Networks GmbH & Co. KG Sitz der Gesellschaft: München / Registered office: Munich Registergericht: München / Commercial registry: Munich, HRA 88537 WEEE-Reg.-Nr.: DE 52984304 Persönlich haftende Gesellschafterin / General Partner: Nokia Siemens Networks Management GmbH Geschäftsleitung / Board of Directors: Hermann Rodler, Olaf Horsthemke Vorsitzender des Aufsichtsrats / Chairman of supervisory board: Herbert Merz Sitz der Gesellschaft: München / Registered office: Munich Registergericht: München / Commercial registry: Munich, HRB 163416 </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------050903050303010609070402--