Merge pull request #2262 from swapdisk/fix_2261

Author: IPvSean

exercises/ansible_ripu/1.3-report/README.md

@@ -28,7 +28,7 @@ In the previous exercise, we used a playbook job template to generate a Leapp pr
 
 - If we we're using the Leapp framework to manually upgrade just a single RHEL host, we could simply get to a shell prompt on the host and look at the local report file output. In [Exercise 1.1, Step 2](../1.1-setup/README.md#step-2---open-a-terminal-session), we learned how to open an ssh session to one of our pet app servers. Follow those steps and after logging in, use this command to review the local Leapp pre-upgrade report file:
 
-  ```
+  ```bash
   less /var/log/leapp/leapp-report.txt
   ```
 

exercises/ansible_ripu/1.5-custom-modules/README.md

@@ -58,13 +58,13 @@ There is a collection of example custom actor at the GitHub repo [oamg/leapp-sup
 
 - Login to one of your pet app servers using the `ssh` command. For example:
 
-  ```
+  ```bash
   ssh tidy-bengal
   ```
 
 - Now we will install the RPM package that provides our custom actor. Run the following command on your pet app server:
 
-  ```
+  ```bash
   sudo yum -y --enablerepo=leapp-supplements install leapp-upgrade-\*-supplements
   ```
 
@@ -74,7 +74,7 @@ There is a collection of example custom actor at the GitHub repo [oamg/leapp-sup
 
 - This is an example of the output you should expect to see if the package is installed successfully:
 
-  ```
+  ```plaintext
   Resolving Dependencies
   --> Running transaction check
   ---> Package leapp-upgrade-el7toel8-supplements.noarch 0:1.0.0-47.demo.el7 will be installed
@@ -111,7 +111,7 @@ There is a collection of example custom actor at the GitHub repo [oamg/leapp-sup
 
 - To demonstrate the custom actor at work, let's create a condition that violates our policy so that an inhibitor finding will be reported. Use this command:
 
-  ```
+  ```bash
   sudo touch /boot/policy-violation
   ```
 
@@ -133,7 +133,7 @@ We are now ready to try running a pre-upgrade report including the checks from o
 
 - Reboot the host to resolve the inhibitor finding. For example:
 
-  ```
+  ```bash
   sudo reboot
   ```
 

exercises/ansible_ripu/1.6-my-pet-app/README.md

@@ -69,7 +69,7 @@ You may want to install a different application, for example, an actual applicat
 
   Login to your pet app server and run these commands:
 
-  ```
+  ```bash
   distver=$(sed -r 's/([^:]*:){4}//;s/(.).*/\1/' /etc/system-release-cpe)
   sudo yum-config-manager --add-repo=https://packages.adoptium.net/artifactory/rpm/rhel/$distver/x86_64
   sudo yum-config-manager --save --setopt=\*adoptium\*.gpgkey=https://packages.adoptium.net/artifactory/api/gpg/key/public
@@ -80,15 +80,15 @@ You may want to install a different application, for example, an actual applicat
 
 - Verify that the temurin-17-jdk package was installed:
 
-  ```
+  ```bash
   rpm -q temurin-17-jdk
   ```
 
   If not, go back and figure out what went wrong.
 
 - Next, we will install the Spring Pet Clinic Sample Application under the home directory of the ec2-user. Run these commands:
 
-  ```
+  ```bash
   cd ~
   git clone https://github.com/spring-projects/spring-petclinic.git
   ```
@@ -97,26 +97,26 @@ You may want to install a different application, for example, an actual applicat
 
 <!-- The EC2 instances for the workshop don't have firewalld, but in case you are using this procedure somewhere that does, use these command to open the firewall:
 
-```
+```bash
 sudo firewall-cmd --add-port=8080/tcp
 sudo firewall-cmd --add-port=8080/tcp --permanent
 ```
 -->
 - We need to start the database server and create the database for our application. Use this command to enable and start the database:
 
-  ```
+  ```bash
   sudo systemctl enable --now mariadb
   ```
 
   Now use the `mysql` command line client to connect to the database server. For example:
 
-  ```
+  ```bash
   mysql --user root
   ```
 
   This should bring you to a `MariaDB [(none)]>` prompt. Enter the following SQL commands at this prompt:
 
-  ```
+  ```plaintext
   CREATE DATABASE IF NOT EXISTS petclinic;
   ALTER DATABASE petclinic DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci;
   GRANT ALL PRIVILEGES ON petclinic.* TO 'petclinic'@'localhost' IDENTIFIED BY 'petclinic';
@@ -126,19 +126,19 @@ sudo firewall-cmd --add-port=8080/tcp --permanent
 
 - Now we are ready to start the application web service. Use this command to run it in the background:
 
-  ```
+  ```bash
   echo 'cd $HOME/spring-petclinic && ./mvnw spring-boot:run -Dspring-boot.run.profiles=mysql >> $HOME/app.log 2>&1' | at now
   ```
 
 - The application will take a couple minute to come up the first time. Check the `app.log` file to follow the progress and verify the web service has started successfully:
 
-  ```
+  ```bash
   tailf ~/app.log
   ```
 
   When you see events listed at the bottom of the log output like this example, that means the application is started successfully and ready for testing:
 
-  ```
+  ```plaintext
   o.s.b.a.e.web.EndpointLinksResolver      : Exposing 13 endpoint(s) beneath base path '/actuator'
   o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
   o.s.s.petclinic.PetClinicApplication     : Started PetClinicApplication in 6.945 seconds (process running for 7.496)
@@ -152,7 +152,7 @@ Now that we have installed our application and verified it is running, it's time
 
 - Use this command to determine the application's external URL:
 
-  ```
+  ```bash
   echo "http://$(curl -s ifconfig.me):8080"
   ```
 
@@ -174,7 +174,7 @@ Right now, our application was started manually. We need to configure the app so
 
 - Use this command to configure a reboot cron entry so the application will be started automatically after every reboot:
 
-  ```
+  ```bash
   echo '@reboot cd $HOME/spring-petclinic && ./mvnw spring-boot:run -Dspring-boot.run.profiles=mysql >> $HOME/app.log 2>&1' | crontab -
   ```
 
@@ -185,7 +185,7 @@ Right now, our application was started manually. We need to configure the app so
 
 - Now reboot the server to verify this works:
 
-  ```
+  ```bash
   sudo reboot
   ```
 
@@ -195,7 +195,7 @@ Right now, our application was started manually. We need to configure the app so
   >
   > Because the external IP addresses of the EC2 instances provisioned for the workshop are dynamically assigned (i.e., using DHCP), it is possible that the web user interface URL might change after a reboot. If you are unable to access the app after the reboot, run this command again to determine the new URL for the application web user interface:
   >
-  > ```
+  > ```bash
   > echo "http://$(curl -s ifconfig.me):8080"
   > ```
   >

exercises/ansible_ripu/2.4-check-pet-app/README.md

@@ -29,7 +29,7 @@ It's time to repeat the testing you did for [Step 3](../1.6-my-pet-app/README.md
   >
   > Because the external IP addresses of the EC2 instances provisioned for the workshop are dynamically assigned (i.e., using DHCP), it is possible that the web user interface URL may change after a reboot. If that happens, run this command at the shell prompt of the app server to determine the new URL for the application web user interface:
   >
-  > ```
+  > ```bash
   > echo "http://$(curl -s ifconfig.me):8080"
   > ```
 

exercises/ansible_ripu/3.1-rm-rf/README.md

@@ -44,7 +44,7 @@ In the next exercise, we will be rolling back the RHEL upgrade on one of our ser
 
 - At the shell prompt, use the `sudo -i` command to switch to the root user. For example:
 
-  ```
+  ```plaintext
   [ec2-user@cute-bedbug ~]$ sudo -i
   [root@cute-bedbug ~]#
   ```
@@ -57,13 +57,13 @@ In the next exercise, we will be rolling back the RHEL upgrade on one of our ser
 
   But what if this package did get removed? Our pet app requires the JDK runtime to function. Without it, our application will be broken. We can simulate this by manually removing the package like this:
 
-  ```
+  ```bash
   dnf -y remove temurin-17-jdk
   ```
 
   Now if you `reboot` the app server, the pet app will not come back up and the following error will be seen at the end of the `~/app.log` file:
 
-  ```
+  ```plaintext
   ...
   which: no javac in (/home/ec2-user/.local/bin:/home/ec2-user/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
   Error: JAVA_HOME is not defined correctly.

exercises/ansible_ripu/3.3-check-undo/README.md

@@ -40,7 +40,7 @@ In this step, we will repeat the observations we made on our host after the upgr
   >
   > Because the external IP addresses of the EC2 instances provisioned for the workshop are dynamically assigned (i.e., using DHCP), it is possible that the web user interface URL may change after a reboot. If that happens, run this command at the shell prompt of the app server to determine the new URL for the application web user interface:
   >
-  > ```
+  > ```bash
   > echo "http://$(curl -s ifconfig.me):8080"
   > ```