Installation stops on Fuel menu even without /root/.showfuelmenu

Bug #1488009 reported by Alexander Evseev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Library (Deprecated)

Bug Description

# fuel --fuel-version
api: '1.0'
astute_sha: 53c86cba593ddbac776ce5a3360240274c20738c
auth_required: true
build_id: 2015-08-23_15-01-12
build_number: '219'
feature_groups:
- mirantis
fuel-agent_sha: 4c2ab9d6c623d345086c6e2874d1df81fd96a942
fuel-library_sha: 3a3ea6d9849bc1ba35c1bd882f0a0678b20d2e51
fuel-nailgun-agent_sha: e01693992d7a0304d926b922b43f3b747c35964c
fuel-ostf_sha: 16839cbf471b7142b04c0d2c2d94786bc486fefe
fuelmain_sha: a494e6628319abfef57e1754f6453cf8f1a4bc65
nailgun_sha: 7790ce872512ecdf21689e6a5f970dd7119febdb
openstack_version: 2015.1.0-7.0
production: docker
python-fuelclient_sha: fc7b63aa6900fe3b2c183108ba6a13e868bc0472
release: '7.0'
release_versions:
  2015.1.0-7.0:
    VERSION:
      api: '1.0'
      astute_sha: 53c86cba593ddbac776ce5a3360240274c20738c
      build_id: 2015-08-23_15-01-12
      build_number: '219'
      feature_groups:
      - mirantis
      fuel-agent_sha: 4c2ab9d6c623d345086c6e2874d1df81fd96a942
      fuel-library_sha: 3a3ea6d9849bc1ba35c1bd882f0a0678b20d2e51
      fuel-nailgun-agent_sha: e01693992d7a0304d926b922b43f3b747c35964c
      fuel-ostf_sha: 16839cbf471b7142b04c0d2c2d94786bc486fefe
      fuelmain_sha: a494e6628319abfef57e1754f6453cf8f1a4bc65
      nailgun_sha: 7790ce872512ecdf21689e6a5f970dd7119febdb
      openstack_version: 2015.1.0-7.0
      production: docker
      python-fuelclient_sha: fc7b63aa6900fe3b2c183108ba6a13e868bc0472
      release: '7.0'

We are using automated deployment tests and removing file /root/.showfuelmenu on first reboot of fuel master (VM deployed by virt-install). But after powering on master node stops on Fuel menu.

bootstrap_admin_node.sh contains code:

showmenu="no"
if [ -f /root/.showfuelmenu ]; then
  . /root/.showfuelmenu
fi

So menu should not be shown if there is no file /root/.showfuelmenu

Contents of root home directory:

[root@fuel ~]# ls -la /root/
total 104
drwxr-xr-x. 3 root root 4096 Aug 24 08:30 .
dr-xr-xr-x. 24 root root 4096 Aug 24 08:44 ..
-rw-------. 1 root root 21368 Aug 24 08:30 anaconda-ks.cfg
-rw-------. 1 root root 5698 Aug 24 08:30 anaconda-post-after-chroot.log
-rw-------. 1 root root 1107 Aug 24 08:30 anaconda-post-before-chroot.log
-rw-------. 1 root root 863 Aug 24 08:30 anaconda-post-partition.log
-rw-r--r--. 1 root root 18 Aug 24 08:30 .bash_logout
-rw-r--r--. 1 root root 176 Aug 24 08:30 .bash_profile
-rw-r--r--. 1 root root 124 Aug 24 08:30 .bashrc
-rw-r--r--. 1 root root 100 Sep 23 2004 .cshrc
-rw-r--r--. 1 root root 16871 Aug 24 08:30 install.log
-rw-r--r--. 1 root root 5332 Aug 24 08:30 install.log.syslog
drwx------. 2 root root 4096 Aug 24 08:44 .ssh
-rw-r--r--. 1 root root 129 Dec 3 2004 .tcshrc

Changed in fuel:
milestone: none → 7.0
assignee: nobody → Fuel Library Team (fuel-library)
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Alex Schultz (alex-schultz) wrote :

When I installed an environment using the 219 iso, the bootstrap_admin_node.sh doesn't reference /root/.showfuelmenu.

The bootstrap_admin_node.sh that is on the fuel-master is actually the https://github.com/stackforge/fuel-main/blob/master/iso/bootstrap_admin_node.docker.sh version that uses /etc/fuel/bootstrap_admin_node.conf

Are you sure that your boostrap_admin_node.sh is referencing the /root/.showfuelmenu file?

There is an open review to revert this change that was added ~3days ago.

https://review.openstack.org/#/c/215737/

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Alexander Evseev (aevseev) wrote :

Not sure. I got this code from git repo…

Revision history for this message
Alexander Evseev (aevseev) wrote :

Yes, now boostrap_admin_node.sh uses /etc/fuel/bootstrap_admin_node.conf

I changed scripts to remove both files, but still no luck. File /etc/fuel/bootstrap_admin_node.conf is in place. Why?
I remove it by issuing command:

sudo rm -f ${fuel_disk_directory}/etc/fuel/bootstrap_admin_node.conf

fuel_disk_directory is mountpoint for VM disk.

But after VM power on file not deleted:

[root@fuel ~]# cat /etc/fuel/bootstrap_admin_node.conf
#Set to yes to run Fuel Setup
#Set to no to accept default settings
showmenu=yes
wait_for_external_config=no

Changed in fuel:
status: Incomplete → Confirmed
status: Confirmed → New
Revision history for this message
Dmitry Ilyin (idv1985) wrote :

Looks like this showmenu is working like this:

First, showmwnu=yes is hardcoded in the boot loader config isolinux/isolinux.cfg and EFI/BOOT/BOOTX64.conf

When kernel is booted showmenu is being written to /root/.showfuelmenu by the ks script. If there is no showmenu in the cmdline it defaults to "no".

Later when bootstrap_admin_node.sh is being run it sources /root/.showfuelmenu and if showmwnu="yes" Fuel menu is run.

So if you don't want to see this menu, as you most likely do, you can:

1) Just sent showmenu to "no" or remove it from cmdline by pressing TAB during the boot loaded phase.

2) Or you can shomehow replace solinux/isolinux.cfg on the iso with the same one but without showmenu hardcoded.

3) Or you can remove /root/.showfuelmenu file after the ks script have finished but before the bootstrap_admin_node.sh by sshing to the running installer.

I guess 2) is the best way if you want to automate the installer. You can even make iso building script accept the parameter that will controll showmenu variable in solinux/isolinux.cfg

Changed in fuel:
status: New → Confirmed
Revision history for this message
Alexander Evseev (aevseev) wrote :

1) As I wrote we use automated tests, we can't change anything in boot loader command line
2) We are part of Mirantis and we test ISOs built by Mirantis as QA, we don't need any sort of custom iso
3) Do you read carefully my first message? We already doing it - delete /root/.showfuelmenu and now also /etc/fuel/bootstrap_admin_node.conf

Revision history for this message
Alexander Evseev (aevseev) wrote :

Sorry guys.

From some change I tried to remove files before VM disk is mounted.

Editing/removing of /etc/fuel/bootstrap_admin_node.conf works.

Changed in fuel:
status: Confirmed → 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.