ci-operator tries to reuse terminating namespaces
0xmichalis opened this issue · comments
2018/09/18 09:29:42 Resolved source https://github.com// to @
2018/09/18 09:29:42 Resolving inputs for the test
2018/09/18 09:29:42 Resolved openshift/release:golang-1.9 to sha256:8332bbe6875aaca035568f9808b7f2146d4e02e7f122669a0c442ea6106a9a50
2018/09/18 09:29:42 Resolved openshift/origin-v3.10:base to sha256:ac253e2792e493b24e632d0ac48c607ce1b250d3b410e1665f250c6965d3a57e
2018/09/18 09:29:42 Resolved inputs, targetting namespace ci-op-2zfnzjw2
2018/09/18 09:29:42 Running [release-inputs], build-azure-image
2018/09/18 09:29:42 Creating namespace ci-op-2zfnzjw2
2018/09/18 09:29:47 Ran for 5s
error: could not initialize namespace: cannot retrieve test namespace: projects.project.openshift.io "ci-op-2zfnzjw2" is forbidden: User "system:serviceaccount:ci:ci-operator" cannot get projects.project.openshift.io in the namespace "ci-op-2zfnzjw2": no RBAC policy matched
{"component":"entrypoint","error":"wrapped process failed: exit status 1","level":"error","msg":"Error executing test process: %v.wrapped process failed: exit status 1","time":"2018-09-18T09:29:47Z"}
ci-op-2zfnzjw2 was in terminating phase and the ci-operator tried to reuse it. If a namespace is terminating, ci-operator should probably create a different one or wait until it's cleaned up to recreate it.
/kind bug
That was resolved in ci-ns-ttl-controller/#2
/close
@droslean: Closing this issue.
In response to this:
That was resolved in ci-ns-ttl-controller/#2
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.