`<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2015-08-14 16:26 GMT+02:00 Dan McDonald <span dir="ltr"><<a href="mailto:danmcd@omniti.com" target="_blank">danmcd@omniti.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Aug 14, 2015, at 6:08 AM, Alexandre Lecuyer <<a href="mailto:alexandre.lecuyer@gmail.com">alexandre.lecuyer@gmail.com</a>> wrote:<br>
><br>
> Hello Dan,<br>
><br>
> I tried to install bloody on openstack.<br>
> The installer boots correctly from the ISO image<br>
> If I start a shell, I can see my target install disk, and create a zpool.<br>
> The network works fine, although I had to configure it manually<br>
><br>
> However, the installer crashes with a python exception right after the "Welcome to OmniOS" screen.<br>
><br>
> /usr/lib/python2.6/vendor-packages/terminalui/inner_window.py, line 318, in activate_object<br>
> raise IndexError(err_msg)<br>
><br>
> I can provide more details if that's interesting<br>
<br>
</span>That would be interesting. I'm particularly interested in whether or not this python error is related to readline or not. Until very recently, readline was accidentally not being linked with the python packages. That has been very recently fixed, after the most recent bloody install media shipped, even.<br>
<br>
So knowing that it's not the recently-re-added readline, I'm curious for more.<br>
<br>
Thanks,<br>
Dan<br>
<br>
</blockquote></div><br><div><div><div><div><div><div><div><div><div><div>I managed to get it installed, the problem occured in the installer, in disk_selection.py, function _show()<br><br></div>in the for loop that starts line 345, we hit this :<br> if disk.disk_prop is None or disk.disk_prop.dev_type is None:<br> continue<br><br></div>So
we never increment disk_index, which causes the exception I mentionned
in my previous email, when we call
self.disk_win.activate_object(self.selected_disk_index)<br><br></div>Looking at disk.disk_prop (DiskProp object), dev_size is properly set, but dev_vendor and dev_type are set to None.<br></div>As far as I can tell, these two fields are displayed by the installer but not used beyond that.<br></div>Setting them to any random field prevents the crash. I was then able to install OmniOS.<br></div>I will have to run another install to try to figure out why they're not set in the first place.<br><br></div>Here's the result after rebooting in the new install :<br>root@unknown:/root# uname -a<br>SunOS unknown 5.11 omnios-3d8d739 i86pc i386 i86pc<br>root@unknown:/root# format<br>Searching for disks...done<br><br><br>AVAILABLE DISK SELECTIONS:<br> 0. c2t0d0 <Unknown-Unknown-0001 cyl 1304 alt 0 hd 255 sec 63><br> /pci@0,0/pci1af4,2@4/blkdev@0,0<br>Specify disk (enter its number): <br><br><br></div>Happy to run further tests if needed, I'll report other issues I can find with the installed system<br><br></div>Cheers,<br></div>Alex</div></div>
`