-
Bug
-
Resolution: Not a Bug
-
Major
-
3.1.0.GA
-
None
-
False
-
None
-
False
0. launch a cluster bot instance (sent slack message to cluster-bot like launch 4.10), and wait 29 mins for it to load
1. Get latest IIB using https://github.com/redhat-developer/devspaces/blob/devspaces-3-rhel-8/product/getLatestIIBs.sh
$➔ ./getLatestIIBs.sh -t 3.1 -q -o 4.10 registry-proxy.engineering.redhat.com/rh-osbs/iib:225160
2. Once cluster bot starts, log in using token or your method of choice:
oc login --token=...
3. Configure pull secrets
# get user and pwd values from this curl --negotiate -u : -X POST -H 'Content-Type: application/json' --data '{"description":"(describe what the token will be used for)"}' https://employee-token-manager.registry.redhat.com/v1/tokens -s | jq oc get secret/pull-secret -n openshift-config -o json | jq -r '.data.".dockerconfigjson"' | base64 -d > authfile podman login --authfile authfile --username "****" --password "****" brew.registry.redhat.io oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=authfile
4. Run Angel's install script https://github.com/redhat-developer/devspaces/blob/devspaces-3-rhel-8/product/installCatalogSourceFromIIB.sh
./installCatalogSourceFromIIB.sh --iib registry-proxy.engineering.redhat.com/rh-osbs/iib:225160 --install-operator devspaces --channel stable
5. Open cluster admin, browse to operatorHub, search for the iib-testing-catalog catalog, and then install devspaces from that. Wait a few minutes.
6. Once that's installed, create a CheCluster from that. Wait a few minutes.
7. Wait for pods to load and the route to exist (see /k8s/ns/openshift-operators/routes in browser, eg., https://console-openshift-console.apps.ci-ln-i899cjt-72292.origin-ci-int-gce.dev.rhcloud.com/k8s/ns/openshift-operators/routes).
8. Open the che-gateway service eg., something like https://devspaces-openshift-operators.apps.ci-ln-i899cjt-72292.origin-ci-int-gce.dev.rhcloud.com/ ... wait for it to load.
9. Open some devfile (I tried the EAP XP3 microprofile one). Wait for it to load.
After elapsed 30 mins or so of combined waits above ...
Then I get this:
Unable to provision networking for DevWorkspace: workspace routing is invalid: the routing does not specify any Che manager in its configuration but there are 2 Che managers in the cluster
