CI E2E selenium tests jobs stuck on the command "ocp.sh --destroy" on OpenShift 3.11
See original GitHub issueDescription
There are E2E selenium test jobs on CI which stuck after the movement to OpenShift 3.11 by default (PR https://github.com/eclipse/che/pull/12357) at the step:
bash ${WORKSPACE}/deploy/openshift/ocp.sh --destroy
For example: https://ci.codenvycorp.com/job/che-integration-tests-multiuser-master-ocp/615/console
[che-integration-tests-multiuser-master-ocp] $ /bin/bash /tmp/jenkins5296940920537614680.sh
Logged into "https://172.29.4.74:8443" as "system:admin" using existing credentials.
You have access to the following projects and can switch between them with 'oc project <projectname>':
default
* eclipse-che
kube-dns
kube-proxy
kube-public
kube-system
myproject
openshift
openshift-apiserver
openshift-controller-manager
openshift-core-operators
openshift-infra
openshift-node
openshift-service-cert-signer
openshift-web-console
Using project "eclipse-che".
adding: che-server-pod.log (deflated 96%)
adding: keycloak.log (deflated 78%)
adding: ocp-events.log (deflated 93%)
adding: postgres.log (deflated 65%)
Logged into "https://172.29.4.74:8443" as "system:admin" using existing credentials.
You have access to the following projects and can switch between them with 'oc project <projectname>':
default
* eclipse-che
kube-dns
kube-proxy
kube-public
kube-system
myproject
openshift
openshift-apiserver
openshift-controller-manager
openshift-core-operators
openshift-infra
openshift-node
openshift-service-cert-signer
openshift-web-console
Using project "eclipse-che".
persistentvolumeclaim "che-data-volume" deleted
persistentvolumeclaim "claim-che-workspace" deleted
persistentvolumeclaim "keycloak-data" deleted
persistentvolumeclaim "keycloak-log" deleted
persistentvolumeclaim "postgres-data" deleted
[PostBuildScript] - [ERROR] Problem occurred: java.lang.InterruptedException
Possible solution: use another command to remove OpenShfit containers:
docker rm -f $(docker ps -aq)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
2035705 – Azure 'Destroy cluster' get stuck ... - Red Hat Bugzilla
Bug 2035705 - Azure 'Destroy cluster' get stuck when the cluster resource ... release image registry.ci.openshift.org/ocp/release@sha256: ...
Read more >CentOS-7
2021-11-18, I want to be added to the OpenShift group: fedora-ci-admins and the OpenShift namespace fedora-ci and fedora-ci-jenkins-prod.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Updated jobs, waiting night cycle to ensure it fixed the problem.
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
days of inactivity and eventually close.Mark the issue as fresh with
/remove-lifecycle stale
in a new comment.If this issue is safe to close now please do so.
Moderators: Add
lifecycle/frozen
label to avoid stale mode.