Description of problem:
[Conformance][templates] test flakiness
Moving to openshift-apiserver
failed condition: no kind is registered for the type v1.Template in scheme \"k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:29
@Adam Can you elaborate on this transfer? That's a client error in a template instance controller test.
Moving this to Templates, though we don't have a clear understanding of where the issue lies at this point in time.
Template instance controller logs have errors like "error syncing namespace, it will be retried: Operation cannot be fulfilled on namespaces "e2e-test-templates-q9c9g": the object has been modified; please apply your changes to the latest version and try again"
We have hope that https://github.com/openshift/openshift-controller-manager/pull/6 fixes this.
Looks like they are gone. Closing.
The tests were never re-enabled:
assigning this to Adam to re-enable the tests. If they are still failing, then he can decide who needs to be chased. But we need to do a better job of connecting the dots when we disable tests in the face of a bug, to ensure the tests get re-enabled when the bug is resolved, in the future.
(note there are numerous tests being skipped for this bug, i only flagged the first one above)
8 of the 11 template extended tests passed in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/24912/pull-ci-openshift-origin-master-e2e-gcp/7434
will start triaging today
re-enabled e2e sufficient verification
WRT doc'ing this bz:
1) mainly, this bug centered around re-enabling existing template tests that were disabled during the 4.2 creation of OCM, followed by a collective forgetting to re-enable
2) the openshift-apiserver change is only needed for k8s 1.18 based master branch i.e. for 4.5 ... I discovered this need as part of the 4.5 dev cycle and it was fixed in the 4.5 cycle;
i.e. it should be considered as part of the overall k82 1.18 bump feature in OCP 4.5, and does not need to be documented as part of errata, etc.
So "NO DOC UPDATED NEEDED"
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.