ci-operator

ci-operator copied to clipboard

Failing to build images in OpenShift 4

3

Running the ci-operator against OpenShift 4 fails to build some images. The `root`, `src` and `bin` images are built correctly but the following image that is based on `base` and...

mgencur

`clonerefs` output is ignored, so tests can run with with incorrect refs

2

We ignore the output of `clonerefs` due to https://github.com/openshift/ci-operator/commit/7ad9489ab5f502d7b40fdd33df6ca508a84f7697 and https://github.com/openshift/ci-operator/commit/9aa7a8a12785307fb33d22920d53fced467187df. That's simply wrong and must be fixed. We should either run `initupload` or write the log and read it...

stevekuznetsov

Detect when a config map doesn't exist on a running pod for > X time, fail

4

A common error mode is forgetting to create a dependent config map. We should do a slightly better job of conveying that condition back (either as a job failure or...

smarterclayton

https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/branch-ci-openshift-cluster-samples-operator-images-master/4 Forgot to do that

smarterclayton

Deleting a pod while the template instance is running doesn't abort the job

1

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_installer/170/pull-ci-origin-installer-e2e-aws-all/1/ ci-operator should have failed, but instead it looks like it hung waiting for something

smarterclayton