Stuck at partitioner when installing ubuntu on OS node

[Sam Stoelinga]

Steps to reproduce:
1. Install Fuel 4.1 on a master node
2. Create an environment with HA setup with Ceph
3. Start adding nodes with custom hardware (Not official Dell servers, but hardware is nearly the same as Dell servers)
4. Deploy

Current result:
Several nodes with custom built hardware get stuck at the partitioner as seen in the youtube video below
A single dell server we have gets installed successfully every time.

Expected result
All servers to be able to be installed

Please see the following video: http://youtu.be/EUGjd-DMuts
Stack trace: https://dl.dropboxusercontent.com/u/7653892/IMG_20140402_203441.jpg

I'm not sure whether this bug is related to Fuel or to my hardware / ubuntu. I will try to intall ubuntu manually and update this bug. I remember that Ubuntu can be installed manually without any problem on the servers with problems.

[Vladimir Kuklin (vkuklin)]

It looks pretty much like kernel bug or hardware one. Closing as Invalid unless you provide more information confirming this is FUEL bug.

[Andrew Woodward (xarses)]

I've seen this occur when there are no disk devices to install on. You can check this by changing to pty2 and doing a ls -l /sys/block. This usually occurs if for whatever reason the disk controller didn't load in the ubuntu 3.2 setup kernel

[Miroslav Anashkin (manashkin)]

I may confirm, if Ubuntu does not include, for instance, drivers for particular RAID controller, it behaves this way.

[Vladimir Kuklin (vkuklin)]

Then we need hardware info of the environment. Sam, please, provide diagnostic snapshot and block device information on the servers you are using.

[Andrew Woodward (xarses)]

confirmed in MOS env, in that case it was missing an adaptec driver. Rebuilding the debian-installer initrd fixed it.

Since debian-installer initrd is using kernel 3.2 we should probably pull it up to 3.8 so it matches installed kernel

[Vladimir Kozhukalov (kozhukalov)]

So, do we know exactly which drivers we need in initrd in order to detect hard drives? Who was that person who re-built initrd to solve the problem? Can we ask him/her which drivers were added?

[Sam Stoelinga (sammiestoel)]

Somehow the launchpad emails came to my spam box. This bug is indeed not a Fuel bug, as I can't even install normal Ubutnu, sorry for the late reply. This may be closer to an ubuntu bug or in the BIOS raid setup.

Do you still want more information? I am currently planning to first restore the servers as we need to use them.