Contents
Find solutions for the most common pitfalls here. If your problem is not mentioned here, checking the log files on either the Administration Server or the OpenStack nodes may help. A list of log files is available at Appendix A, Log Files.
Please check the script's log file at
/var/log/chef/install.log
for error messages.
In order to activate the bastion network, you need to run two additional commands after having run install-chef-suse.sh:
crowbar network -U crowbar -P crowbar allocate_ip default $(hostname -f) bastion admin chef-client
-n
shows no gateway for the bastion
network.
Make sure the value for the bastion network's
"router_pref":
entry in
/opt/dell/chef/data_bags/crowbar/bc-template-network.json
is set to a lower value than the
"router_pref":
entry for the admin network.
No, once you have run install-chef-suse.sh you cannot change the hostname anymore. Services like Crowbar, Chef, and the RabbitMQ will fail when having changed the hostname.
Tampered with
cookie
error:
You probably have an old cookie in your browser from a previous Chef
installation on the same IP. Remove the cookie named
_chef_server_session_id
and try again.
root
?
By default you cannot directly log in to a node as root
, because
the nodes were set up without a root
password. You can only log in
via SSH from the Administration Server. You should be able to log in to a node with
ssh root@NAME
where
NAME
is the name (alias) of the node.
If name resolution does not work, go to the Crowbar Web interface and
open the root
.
Make sure to change the boot order in the BIOS of the node, so that the first boot option is to boot from the network/PXE boot.
The SLEShammer image has no root
password set, so
log in in for debugging purposes is not possible. To set a root
password for the SLEShammer for the node that hangs, proceed as follows:
Make sure you know the MAC address of the hanging node
Log in to the Administration Server as root
Create a directory named
/updates/d<HOSTNAME>
where <HOSTNAME>
is the MAC address
of the hanging node with lowercase letters
(e.g. de-9a-88-bd-ff-c1
). Note that the MAC
address is always prefixed by the lowercase letter
d
.
Create a hook script
/updates/
with the following content:
<HOSTNAME>
/discovery-pre.hook
#!/bin/bash
echo "linux
" | passwd --stdin root
In this example, the root
password is set to
linux
. You may want to change it to a more
secure password.
Log in to the Crowbar Web interface and delete the hanging node from the pool as described in Section 4.4, “Editing Allocated Nodes”.
Reboot the hanging node to restart the hardware detection. Now you
will be able to log in to the SLEShammer image as root
using
the password supplied by the hook script. In order to find out why
the node hangs, you may want to look at
/var/log/chef/client.log
first.
Could not find kernel
image: ../suse-11.2/install/boot/x86_64/loader/linux
The installation repository at
/srv/tftpboot/suse-11.2/install
on the Administration Server
has not been set up correctly to contain the SUSE Linux Enterprise Server 11 SP2 installation
media. Please review the instructions at Section 3.2.2, “Setting Up Local Repositories”.
Unpacking initramfs
during PXE boot.
The node probably does not have enough RAM. You need at least 2 GB RAM.
Executing AutoYast script:
/var/adm/autoinstall/init.d/crowbar_join:
Log in to the node as root
and check the log files at
/var/log/crowbar-join*
for errors.
Check the Chef client logs located on the node(s) affected by the proposal
(/var/log/chef/client.log
), and also the logs of
the service that failed to be deployed. Additional information may be
gained from the Crowbar Web UI logs on the Administration Server. For a list of log
file locations refer to Appendix A, Log Files.
Whenever you contact support to help you with a problem on SUSE Cloud, it is strongly recommended that you gather as much information about your system and the problem as possible. For this purpose SUSE Cloud ships with a tool called supportconfig. It gathers system information such as the current kernel version being used, the hardware, RPM database, partitions, and other items. supportconfig also collects the most important log files, making it easier for the supporters to identify and solve your problem.
It is recommended to always run supportconfig on the Administration Server as well as on the Controller Node. If a Compute Node or a Storage Node is part of the problem, run supportconfig on the affected node as well. For details on how to run supportconfig, please refer to http://www.suse.com/documentation/sles11/book_sle_admin/data/cha_adm_support.html.