Mission Specialist
Mission Specialist
  • 667 Views

DO288 OpenShift Dev lab docker-build failed to deploy. It timed out.

I tried DO288 OpenShift Dev lab docker-build three times without luck.

New app echo was built  successfully but deployment timed out after 10 mins (seen from oc get pods -w).

I retried twice but still no luck:

1) deleted project ${RHT_OCP4_DEV_USER}-docker-build;
2) deleted my lab environment, reprovisioned.

Does anyone has any suggestions?

Labels (2)
Tags (1)
0 Kudos
4 Replies
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 663 Views

Re: DO288 OpenShift Dev lab docker-build failed to deploy. It timed out.

Which version of the classroom are you using...we just released a new version last Friday.

0 Kudos
Reply
Loading...
Highlighted
Mission Specialist
Mission Specialist
  • 657 Views

Re: DO288 OpenShift Dev lab docker-build failed to deploy. It timed out.

Hi Jim,

I selected my DO288 a few weeks ago.  

On advice from a colleague, I deleted the project and re-did the exercise.  Then  run
oc get ev
which shows the following errors:

FailedScheduling:  0/6 nodes are available:
3 insufficient memory
3 nodes had taints that the pod did'nt tolerate

This seems to say there are no available nodes to deploy!
Jack

 

 

0 Kudos
Reply
Loading...
Highlighted
Mission Specialist
Mission Specialist
  • 656 Views

Re: DO288 OpenShift Dev lab docker-build failed to deploy. It timed out.

Hi Jim

Just to be clear.  I selected my DO288R course a few weeks ago but I only started to study it since yesterday.  

The issue I encountered is current.

Is it possible to reselect a new DO288R afresh and start again?

 

Jack

0 Kudos
Reply
Loading...
Highlighted
Mission Specialist
Mission Specialist
  • 651 Views

Re: DO288 OpenShift Dev lab docker-build failed to deploy. It timed out.

Jim,

Update:  the availability of nodes seems to have been rectified partially (2 nodes available now).  My deployment succeeded without my intervention.

Hope a robust fix is put in place so that we do not have node availability issue again.

Jack

0 Kudos
Reply
Loading...
Join the discussion
You must log in to join this conversation.