Merge pull request #37226 from stevsmit/BZ1893593

Adds sudo to two commands

Author: mburke5678

modules/ipi-install-troubleshooting-bootstrap-vm-inspecting-logs.adoc

@@ -22,47 +22,47 @@ The `ipa-downloader` and `coreos-downloader` containers download resources from
 
 . Log in to the bootstrap VM:
 +
-[source,bash]
+[source,terminal]
 ----
 $ ssh [email protected]
 ----
 
 . Check the status of the `ipa-downloader` and `coreos-downloader` containers within the bootstrap VM:
 +
-[source,bash]
+[source,terminal]
 ----
-[core@localhost ~]$ podman logs -f ipa-downloader
+[core@localhost ~]$ sudo podman logs -f ipa-downloader
 ----
 +
-[source,bash]
+[source,terminal]
 ----
-[core@localhost ~]$ podman logs -f coreos-downloader
+[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,bash]
+[source,terminal]
 ----
 [core@localhost ~]$ journalctl -xe
 ----
 +
-[source,bash]
+[source,terminal]
 ----
 [core@localhost ~]$ journalctl -b -f -u bootkube.service
 ----
 
 . Verify all the pods, including `dnsmasq`, `mariadb`, `httpd`, and `ironic`, are running:
 +
-[source,bash]
+[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 log of the `ironic-api`, execute the following:
 +
-[source,bash]
+[source,terminal]
 ----
 [core@localhost ~]$ sudo podman logs <ironic-api>
 ----