// Module included in the following assemblies:
// 
//installing/installing_bare_metal/ipi/ipi-install-troubleshooting.adoc

:_mod-docs-content-type: PROCEDURE
[id="ipi-install-troubleshooting-bootstrap-vm-inspecting-logs_{context}"]
= Inspecting logs

When experiencing issues downloading or accessing the {op-system} images, first verify that the URL is correct in the `install-config.yaml` configuration file.

.Example of internal webserver hosting {op-system} images
[source,yaml]
----
bootstrapOSImage: http://<ip:port>/rhcos-43.81.202001142154.0-qemu.<architecture>.qcow2.gz?sha256=9d999f55ff1d44f7ed7c106508e5deecd04dc3c06095d34d36bf1cd127837e0c
clusterOSImage: http://<ip:port>/rhcos-43.81.202001142154.0-openstack.<architecture>.qcow2.gz?sha256=a1bda656fa0892f7b936fdc6b6a6086bddaed5dafacedcd7a1e811abb78fe3b0
----

The `coreos-downloader` container downloads resources from a webserver or from the external link:https://quay.io[quay.io] registry, whichever the `install-config.yaml` configuration file specifies. Verify that the `coreos-downloader` container is up and running and inspect its logs as needed.

.Procedure

. Log in to the bootstrap VM:
+
[source,terminal]
----
$ ssh core@172.22.0.2
----

. Check the status of the `coreos-downloader` container within the bootstrap VM by running the following command:

+
[source,terminal]
----
[core@localhost ~]$ sudo podman logs -f coreos-downloader
----
+
If the bootstrap VM cannot access the URL to the images, use the `curl` command to verify that the VM can access the images.

. To inspect the `bootkube` logs that indicate if all the containers launched during the deployment phase, execute the following:
+
[source,terminal]
----
[core@localhost ~]$ journalctl -xe
----
+
[source,terminal]
----
[core@localhost ~]$ journalctl -b -f -u bootkube.service
----

. Verify all the pods, including `dnsmasq`, `mariadb`, `httpd`, and `ironic`, are running:
+
[source,terminal]
----
[core@localhost ~]$ sudo podman ps
----

. If there are issues with the pods, check the logs of the containers with issues. To check the logs of the `ironic` service, run the following command:
+
[source,terminal]
----
[core@localhost ~]$ sudo podman logs ironic
----