Troubleshooting Oracle Linux Upgrade on VM

After upgrading, if SCM is inaccessible and you receive the following response:

ERR_CONNECTION_REFUSED - This site can't be reached

Then wait for a few minutes after the "Run apply" job completes, as SCM is deployed through the cloud-init script it takes time to complete after the "Run apply" job completes. If the error persists even after this period, follow these steps to diagnose and resolve the issue:

SSH in to the SCM instance.
Check the status of the SCM container:
```
sudo podman ps
```

Troubleshoot based on the result of the command:

If this command throws the following error:
```
bash: podman: command not found
```
It implies that the cloud-init script is still running and the Podman installation hasn't started. Check the cloud-init-output.log for progress details, as follows:
```
vi /var/log/cloud-init-output.log
```
If the log indicates that the cloud-init script was skipped, that is, the Podman installation did not occur yet the script was marked as completed, then run the cloud-init script manually as follows:
```
ssh -i <ssh Private Key> opc@<SCM Host IP>
curl --fail -H "Authorization: Bearer Oracle" -L0 http://169.254.169.254/opc/v2/instance/metadata/user_data | base64 --decode > /tmp/user-init.sh
sudo bash -x /tmp/user-init.sh
```
Enter 'n' when prompted for overwriting the ssh key.
Note: Running this script multiple times creates duplicate entries for the "DEFAULT" profile in the ~/.oci/config file, resulting in SCM container startup failure. To resolve this issue:
1. Edit the ~/.oci/config file manually to delete the duplicate "DEFAULT" profile entries.
2. Reload systemd:
```
sudo systemctl daemon-reload
```
3. Restart the SCM container:
```
sudo systemctl restart cloudmanager
```
If the status of the SCM container indicates that the SCM container is stopped or restarting, check the logs:
```
sudo podman logs -f cloudmanager
```
If the container logs shows the NotAuthenticated 401 error, it implies that the OCI config or fingerprint passed during SCM stack deployment is incorrect. To resolve the issue:
1. Update the OCI config in the /home/opc/.oci/config file with the correct parameter values.
2. Restart the SCM container:
```
sudo systemctl restart cloudmanager
```
If it does not list the SCM container, check the status of the container service:
```
sudo systemctl status cloudmanager
```
If the command returns the following message:
```
cloudmanager.service: Start request repeated too quickly.
cloudmanager.service: Failed with result 'exit-code'.
Failed to start Podman cloudmanager.service.
```
The error indicates that the SCM container is repeatedly restarting. To diagnose and resolve the issue, check the container logs and analyze the issue. If the error is NotAuthenticated 401, follow the above steps to resolve.
For more information on any other issues, see Troubleshooting a Siebel Cloud Manager Instance or Requested Environment.