[OmniOS-discuss] Anyone try the new bloody ISO on OpenStack/KVM or Linux/KVM
Alexandre Lecuyer
alexandre.lecuyer at gmail.com
Fri Aug 14 15:13:10 UTC 2015
2015-08-14 16:26 GMT+02:00 Dan McDonald <danmcd at omniti.com>:
>
> > On Aug 14, 2015, at 6:08 AM, Alexandre Lecuyer <
> alexandre.lecuyer at gmail.com> wrote:
> >
> > Hello Dan,
> >
> > I tried to install bloody on openstack.
> > The installer boots correctly from the ISO image
> > If I start a shell, I can see my target install disk, and create a zpool.
> > The network works fine, although I had to configure it manually
> >
> > However, the installer crashes with a python exception right after the
> "Welcome to OmniOS" screen.
> >
> > /usr/lib/python2.6/vendor-packages/terminalui/inner_window.py, line 318,
> in activate_object
> > raise IndexError(err_msg)
> >
> > I can provide more details if that's interesting
>
> 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.
>
> So knowing that it's not the recently-re-added readline, I'm curious for
> more.
>
> Thanks,
> Dan
>
>
I managed to get it installed, the problem occured in the installer, in
disk_selection.py, function _show()
in the for loop that starts line 345, we hit this :
if disk.disk_prop is None or disk.disk_prop.dev_type is None:
continue
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)
Looking at disk.disk_prop (DiskProp object), dev_size is properly set, but
dev_vendor and dev_type are set to None.
As far as I can tell, these two fields are displayed by the installer but
not used beyond that.
Setting them to any random field prevents the crash. I was then able to
install OmniOS.
I will have to run another install to try to figure out why they're not set
in the first place.
Here's the result after rebooting in the new install :
root at unknown:/root# uname -a
SunOS unknown 5.11 omnios-3d8d739 i86pc i386 i86pc
root at unknown:/root# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c2t0d0 <Unknown-Unknown-0001 cyl 1304 alt 0 hd 255 sec 63>
/pci at 0,0/pci1af4,2 at 4/blkdev at 0,0
Specify disk (enter its number):
Happy to run further tests if needed, I'll report other issues I can find
with the installed system
Cheers,
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20150814/c2d297b2/attachment.html>
More information about the OmniOS-discuss
mailing list