Comment 14 for bug 1610967

Hello Koren,

I am still looking forward to your initrd.img file. Please attach it to the bug.

I built the initrd-new.img, which outputs the debug messages to console during the boot.

Please copy the initrd-new.img into the folder
/var/www/nailgun/bootstraps/active_bootstrap/
rename it to initrd.img and run the following command (to update the initrd.img in the cache):

"fuel-bootstrap activate <id-of-your-active-bootstrap>"

In my case (based on the output of the "fuel-bootstrap list" command below):
$ fuel-bootstrap list
+--------------------------------------+--------------------------------------+--------+
| uuid | label | status |
+--------------------------------------+--------------------------------------+--------+
| 4314e0cf-4e7c-4986-8bf1-2b7e9058e4a2 | 4314e0cf-4e7c-4986-8bf1-2b7e9058e4a2 | active |
+--------------------------------------+--------------------------------------+--------+

the command should be:

fuel-bootstrap activate 4314e0cf-4e7c-4986-8bf1-2b7e9058e4a2

In your case the ID could be different.

After that please add "debug" key to the kernel parameters passing on boot and reboot one node.
You will see in the output what is going on during init script.

Please attach (to the bog) the screen-shot where is the node get stuck before reboot by timeout.

Looking forward to your update,
Albert