-
Story
-
Resolution: Done
-
Major
-
None
-
None
As per title, we need to have our CI running on top of OpenShift 4.0.
[SRVKS-2] Setup CI for the release 0.3 branch on OpenShift 4.0
Markus Thömmes (Inactive)
added a comment - **TestHelloWorldFromShell might have gotten into there through rebasing and retrying different things to fix our resource issues.
Markus Thömmes (Inactive)
added a comment - ** TestHelloWorldFromShell might have gotten into there through rebasing and retrying different things to fix our resource issues. Markus Thömmes (Inactive)
added a comment - Made a big step forward and finally had a "clean" run only containing genuine errors:
- TestContainerErrorMsg (360.18s) errorcondition_test.go:82: Failed to validate configuration state: timed out waiting for the condition
- TestRunLatestService (67.08s) service_test.go:173: imageDigest not present for revision test-run-latest-service-lyyojzam-00001
- TestHelloWorldFromShell (1.96s) helloworld_shell_test.go:104: Error running kubectl: error: error validating "/tmp/helloworld088681814": error validating data: ValidationError(Configuration): unknown field "spec" in dev.knative.serving.v1alpha1.Configuration; if you choose to ignore these errors, turn validation off with --validate=false
Markus Thömmes (Inactive)
added a comment - Made a big step forward and finally had a "clean" run only containing genuine errors:
TestContainerErrorMsg (360.18s) errorcondition_test.go:82: Failed to validate configuration state: timed out waiting for the condition
TestRunLatestService (67.08s) service_test.go:173: imageDigest not present for revision test-run-latest-service-lyyojzam-00001
TestHelloWorldFromShell (1.96s) helloworld_shell_test.go:104: Error running kubectl: error: error validating "/tmp/helloworld088681814": error validating data: ValidationError(Configuration): unknown field "spec" in dev.knative.serving.v1alpha1.Configuration; if you choose to ignore these errors, turn validation off with --validate=false
We've got all issues resolved.
TestContainerErrorMsg/TestRunLatestService were issues with the internal registry which we resolved by obtaining the correct certificate (thanks bbrownin@redhat.com!)**
TestHelloWorldFromShell is a kubectl version mismatch (the version in CI is too new for the server I believe). I Switched this test to use oc throughout (which makes sense for our CI anyway).