From dfddcd568c7719001a44ab128def90f0191c19ec Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Tue, 8 Mar 2016 14:46:18 +0100 Subject: [PATCH] Update the troubleshooting guide Drop information only relevant to the old ramdisk. Change-Id: I248a286069ab21ef07942b4c85eae9fe283e40f6 --- doc/source/troubleshooting.rst | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/doc/source/troubleshooting.rst b/doc/source/troubleshooting.rst index 39e3c8379..b6825fc02 100644 --- a/doc/source/troubleshooting.rst +++ b/doc/source/troubleshooting.rst @@ -95,13 +95,26 @@ ramdisk or to boot them, make sure that: #. ``pxelinux.cfg/default`` within TFTP root contains correct reference to the kernel and ramdisk. +.. note:: + If using iPXE instead of PXE, check the HTTP server logs and the iPXE + configuration instead. + Troubleshooting ramdisk run ^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Connect to the remote console as described in `Troubleshooting PXE boot`_ to -see what is going on with the ramdisk. The ramdisk drops into emergency shell -on failure, which you can use to look around. There should be file called -``logs`` with the current ramdisk logs. +First, check if the ramdisk logs were stored locally as described in the +`Troubleshooting data processing`_ section. If not, ensure that the ramdisk +actually booted as described in the `Troubleshooting PXE boot`_ section. + +Finally, you can try connecting to the IPA ramdisk. If you have any remote +console access to the machine, you can check the logs as they appear on the +screen. Otherwise, you can rebuild the IPA image with your SSH key to be able +to log into it. Use the `dynamic-login`_ or `devuser`_ element for a DIB-based +build or put an authorized_keys file in ``/usr/share/oem/`` for a CoreOS-based +one. + +.. _devuser: http://docs.openstack.org/developer/diskimage-builder/elements/devuser/README.html +.. _dynamic-login: http://docs.openstack.org/developer/diskimage-builder/elements/dynamic-login/README.html .. _ubuntu-dns: