-
Bug
-
Resolution: Done
-
Minor
-
DO280 - OSE 3.0 1 20151019
-
None
-
5
-
en-US (English)
URL:
Reporter RHNID:
Section: -
Language: en-US (English)
Workaround:
Description: Guided Exercise: Creating a Persistent Registry
1.1. As the OSE instance administrator, find the registry pod name:
expected output has a reference to oserouter
s/oserouter/trainingrouter
2.5. Umount /mnt.
Should be done on node
code box prompt is wrong
/s/master/node
3.1. Edit the PV resource definition file ...
Clarify that this should be done back on master (previous step was on node)
4.1. Create the PersistentVolumeClaim using the provided JSON resource definition file:
What? we are creating without ever looking at the json first?
5.3. Verify DeploymentConfig docker-registry started a new registry pod:
Why the watch command? does it really take that long?