You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Login to the cluster on terminal using oc login command
Steps
make e2e USE_EXISTING_CLUSTER=true
Expected Result
All test should pass
Actual Result
• Failure [300.002 seconds]
Jenkins controller
/usr/local/go/src/github.com/redhat-developer/jenkins-operator/controllers/integration_test.go:31
When Creating a Jenkins Instance with Default CASC and Backup Configured
/usr/local/go/src/github.com/redhat-developer/jenkins-operator/controllers/integration_test.go:38
Deployment Is Ready (jenkins-with-all) [It]
/usr/local/go/src/github.com/redhat-developer/jenkins-operator/controllers/integration_test.go:107
Timed out after 300.000s.
Expected
<int32>: 0
to equal
<int32>: 1
/usr/local/go/src/github.com/redhat-developer/jenkins-operator/controllers/integration_test.go:327
------------------------------
Jenkins controller When Creating a Jenkins Instance with Default CASC and Backup Configured
Namespace should be deleted (jenkins-with-all)
/usr/local/go/src/github.com/redhat-developer/jenkins-operator/controllers/integration_test.go:113
STEP: Deleting Namespace if it is present
•STEP: tearing down the test environment
Summarizing 1 Failure:
[Fail] Jenkins controller When Creating a Jenkins Instance with Default CASC and Backup Configured [It] Deployment Is Ready (jenkins-with-all)
/usr/local/go/src/github.com/redhat-developer/jenkins-operator/controllers/integration_test.go:327
Ran 13 of 13 Specs in 359.221 seconds
FAIL! -- 12 Passed | 1 Failed | 0 Pending | 0 Skipped
--- FAIL: TestAPIs (359.22s)
FAIL
Ginkgo ran 1 suite in 6m8.644521218s
Test Suite Failed
make: *** [Makefile:17: e2e] Error 1
Test are failing as the deployment is not Ready
The text was updated successfully, but these errors were encountered:
Prerequisite
oc login
commandSteps
make e2e USE_EXISTING_CLUSTER=true
Expected Result
Actual Result
Test are failing as the deployment is not Ready
The text was updated successfully, but these errors were encountered: