In this lab scenario, a containerized application is not working properly and needs to be fixed. Using the various logs available to us, we will find the issue, correct it, and start the application.
*This lab is not approved or sponsored by Red Hat.*
Due to limitations in the A Cloud Guru Cloud Playground environment, we are unable to provide a hands-on experience for this lab.
1. To complete this lab, you must first register for a Red Hat Developer login on the ***[Red Hat login page](https://developers.redhat.com/login)***.
2. Once registered, you may complete the lab steps using one of the following methods:
* Download ***[Red Hat’s CodeReady Containers](https://cloud.redhat.com/openshift/install/crc/installer-provisioned)*** and install them locally on your own system.
* Log in to your Red Hat Developer account and use a ***[Red Hat-provided OpenShift sandbox](https://developers.redhat.com/products/codeready-containers/overview)***.
Solutions for CodeReady Containers and the Red Hat OpenShift sandbox are available in this lab.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Create the New Project
Create a new project with the name
bad-mysql.Note: This section only applies to local users of the OpenShift environment. Remote access users should skip this section.
- Replicate the Issue with the Application
Replicate the problem by creating a new MySQL application with the following command:
oc new-app --name=secret-db mysql mysql_root_pass=supersecret -l app=secret-db- Troubleshoot and Fix the Application
- Review the logs for the failing application to find the issue.
- Fix the issue that is causing the application to fail.
- Verify the Application Is Running
Connect to the new application pod and verify the MySQL instance is working.
