-
Story
-
Resolution: Done
-
Major
-
DO280 - OCP 3.5 1 20170829
-
None
-
ILT, ROLE, VT
-
en-US (English)
URL:
Reporter RHNID: olafbohlen
Section: Lab - Managing Application Deployments
Language: en-US (English)
Workaround: Fix in the lab: oc login -u admin
oc project default
oc edit dc docker-registry
(fix region=applications)
wait till docker-registry is back up
change back to the project:
oc project schedule-review (which should be manage-review as stated in other issues)
oc rollout latest version
check that pods are running.
At clean-up do not forget to change back the region tag in docker-registry's dc to infra!
Description: If delegates follow the instructions for the lab of chapter 7 and they have unfortunately running their docker-registry pod on node2, which will be drained, OpenShift cannot redeploy the pod. The reason is that the nodeSelector in the docker-registry dc requires region=infra, which no nodes have at this point (both are set to applications at this point).