Launching fuel with quick-start scripts silently requires vnc connection

Bug #1307187 reported by Eugene Nikanorov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
Unassigned

Bug Description

Starting fuel installation requires pressing <enter> on the first screen of computer where fuel is installed.
In case when such computer doesn't have a monitor, vnc connection is required.
Need to reflect that in scripts and in quick start guide.

Revision history for this message
Mike Scherbakov (mihgen) wrote :

Why would you need to press Enter?
virtualbox scripts https://github.com/stackforge/fuel-main/tree/master/virtualbox install Fuel master in unattended way, no keypresses is required by default. You will get default network configuration for master node though.

If you are about to change it, you will need to work via console, yes.

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

I'm working with http://software.mirantis.com/quick-start/ and 4.1 image.

When running launch.sh, loading process "hangs" after vm start.
After I amended the script with options that allows to connect to started vm with vnc, I'm seeng a screen that awaits pressing <enter>.

After a few tries I've noticed that in fact it waits for enter for some time, and then starts installing OS, but then fails on a step of checking CPU architecture.

I'm trying to run it on a VPS (kvm virtualization); so apparently VirtualBox can't offer x86_64 cpu without hardware support.

So I think this particular issue can be closed as invalid, however I think quick that quick-start guide should reflect that quick-start scripts require physical box or at least exported cpu virtualization capabilities.

Changed in fuel:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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