Lab pods do not work

[Nikkie]

The steps don't work in step 8.4 onwards in DO280 for V4.12. Even after copy and pasting the solution files for deployment.yaml, the pods keep restarting and ending up as CrashLoopBackOff.

2024-01-31 08:01:00.675  INFO 1 --- [           main] com.redhat.beeper.BeeperApplication      : Started BeeperApplication in 33.686 seconds (JVM running for 35.684)
2024-01-31 08:01:54.260  INFO 1 --- [ionShutdownHook] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default'
2024-01-31 08:01:54.263  INFO 1 --- [ionShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown initiated...
2024-01-31 08:01:54.275  INFO 1 --- [ionShutdownHook] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Shutdown completed.

 
NAME                          READY   STATUS             RESTARTS        AGE
beeper-api-5fdbb59b79-ms474   0/1     CrashLoopBackOff   6 (2m46s ago)   13m

[Chetan_Tiwary_]

Hello @Nikkie !

Thanks for reaching out !

In which chapter and section were you getting this error ? Have you already raised a support case regarding this ? 

[Wander]

The startup probe in the solution file tries to use HTTP, not HTTPS as it should (and what the books says), hence the HTTP 400 errors in your events. After fixing this your deployment won't progress, since it is set to RollingUpdate, and the extra pod does not fit in the quota you setup earlier. So you can either (temporarily) increase the quota, or scale the beeper-api deployment to zero and then back to one.

The following info will give you all you need to know when troubleshooting this:

oc get events --field-selector involvedObject.kind==Deployment,involvedObject.name==beeper-api

oc get events --field-selector involvedObject.kind==ReplicaSet