Unable to find Kickstart file on boot

Bug #1503009 reported by Rich
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
Svetlana Karslioglu
6.1.x
Won't Fix
Medium
Fuel Documentation Team
7.0.x
Won't Fix
Medium
Svetlana Karslioglu

Bug Description

Mirantis no longer provides a download for a .img to create a bootable USB drive. I have downloaded the .iso for both 6.1 and 7.0 and used multiple windows applications to burn .iso to USB drive. When the server boots, I select USB install from the grub boot loader and after a few seconds, it says "Unable to find kickstart file".

Changed in fuel:
milestone: none → 8.0
tags: added: customer-found
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :
Revision history for this message
Rich (pixelbrilliance) wrote :

Stanislaw,

I'm using windows, dd is for *NIX systems. Is dd currently the only supported way to accomplish this task?

Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Rich, you can try http://www.chrysocome.net/dd or use any tool that will copy ISO sector-by-sector to USB drive (it is exactly what dd does).

Revision history for this message
Alex Schultz (alex-schultz) wrote :

This should be updated in the documentation and not closed. We should explicitly state that DD or block level copying is required.

Revision history for this message
Rich (pixelbrilliance) wrote :

Stanislaw,

After reading through the documentation for http://www.chrysocome.net/dd, I came up with the following:

dd if=d:\MirantisOpenStack-7.0.iso of=\\.\e: --progress

The drive "\\.\e:" is assigned to my USB drive as indicated by the output of "dd --list". Once it said it completed successfully, I tried booting the server with the USB drive, but it just loads straight into the current OS. Does this USB drive need to be made bootable first?

Some comprehensive documentation would be much appreciated.

Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: docs
Dmitry Pyzhov (dpyzhov)
tags: added: area-docs
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

We no longer support MOS5.1, MOS6.0, MOS6.1
We deliver only Critical/Security fixes to MOS7.0, MOS8.0.
We deliver only High/Critical/Security fixes to MOS9.2.

Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.