openstack/bifrost
Code Issues Proposed changes

Update troubleshooting text for custom IPA images

Browse Source 
Additional text to help users understand how to gain access to a
running IPA image for troubleshooting purposes.

Change-Id: I337f02f7fa496312893bff8bb2bfb67dadb67cd9
This commit is contained in:
Julia Kreger 2015-10-15 08:20:15 -04:00
parent af7d9ac2e9
commit 5f6b94db45
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
troubleshooting.rst
View File

@ -106,8 +106,8 @@ Obtaining IPA logs via the console
You will want to view the system console occurring. If possible, you
may wish to use ``ipmitool`` and write the output to a log file.
Gaining access via SSH to the node running IPA
==============================================
Gaining access via SSH to the node running IPA on CoreOS based images
=====================================================================
If you wish to SSH into the node in order to perform any sort of post-mortem,
you will need to do the following:
@ -124,6 +124,22 @@ you will need to do the following:
3) ``ssh -l core <ip-address-of-node>``
Gaining access via SSH to the node running IPA for custom images
================================================================
Custom built images will require a user to be burned into the image.
Typically a user would use the diskimage-builder devuser element
to achieve this. More detail on this can be located at::
https://github.com/openstack/diskimage-builder/tree/master/elements/devuser
Example::
export DIB_DEV_USER_USERNAME=customuser
export DIB_DEV_USER_PWDLESS_SUDO=yes
export DIB_DEV_USER_AUTHORIZED_KEYS=$HOME/.ssh/id_rsa.pub
disk-image-create -o /path/to/custom-ipa debian ironic-agent devuser
************************************
``ssh_public_key_path is not valid``
************************************