Skip to content

Latest commit

 

History

History
76 lines (68 loc) · 2.7 KB

installation-bootstrap-gather.adoc

File metadata and controls

76 lines (68 loc) · 2.7 KB

Gathering logs from a failed installation

If you gave an SSH key to your installation program, you can gather data about your failed installation.

Note

You use a different command to gather logs about an unsuccessful installation than to gather logs from a running cluster. If you must gather logs from a running cluster, use the oc adm must-gather command.
Prerequisites

  • Your {product-title} installation failed before the bootstrap process finished. The bootstrap node must be running and accessible through SSH.

  • The ssh-agent process is active on your computer, and you provided both the ssh-agent process and the installation program the same SSH key.

  • If you tried to install a cluster on infrastructure that you provisioned, you must have the fully-qualified domain names of the control plane, or master, machines.

Procedure

  1. Generate the commands that are required to obtain the installation logs from the bootstrap and control plane machines:

    • If you used installer-provisioned infrastructure, run the following command:

      $ ./openshift-install gather bootstrap --dir=<directory> (1)

      1. installation_directory is the directory you stored the {product-title} definition files that the installation program creates.

        For installer-provisioned infrastructure, the installation program stores information about the cluster, so you do not specify the host names or IP addresses

    • If you used infrastructure that you provisioned yourself, run the following command:

      $ ./openshift-install gather bootstrap --dir=<directory> \ (1)
    --bootstrap <bootstrap_address> \ (2)
    --master <master_1_address> \ (3)
    --master <master_2_address> \ (3)
    --master <master_3_address>" (3)

      1. installation_directory is the directory you stored the {product-title} definition files that the installation program creates.

      2. <bootstrap_address> is the fully-qualified domain name or IP address of the cluster’s bootstrap machine.

      3. For each control plane, or master, machine in your cluster, replace <master_*_address> with its fully-qualified domain name or IP address.

        Note

        A default cluster contains three control plane machines. List all of your control plane machines as shown, no matter how many your cluster uses.

    The command output resembles the following example:

    INFO Pulling debug logs from the bootstrap machine
INFO Bootstrap gather logs captured here "<directory>/log-bundle-<timestamp>.tar.gz"

    If you open a Red Hat support case about your installation failure, include the compressed logs in the case.