-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.19.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Checked [sig-arch][Late][Jira:"kube-apiserver"] all registered tls artifacts must have no metadata violation regressions [Suite:openshift/conformance/parallel] test results, some tls artifacts have metadata violation regressions
Version-Release number of selected component (if applicable):
4.19
How reproducible:
always
Steps to Reproduce:
Checked one CI job for case,
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview/1906886485508886528
Error logs:
Run #0: Failed expand_less36s{ flake: requirement/ownership: --namespace=kube-system configmap/extension-apiserver-authentication regressed and does not have value set requirement/ownership: --namespace=openshift-apiserver configmap/image-import-ca regressed and does not have value set requirement/ownership: --namespace=openshift-config-managed configmap/image-registry-ca regressed and does not have value set requirement/ownership: --namespace=openshift-config-managed configmap/merged-trusted-image-registry-ca regressed and does not have value set requirement/ownership: --namespace=openshift-image-registry configmap/image-registry-certificates regressed and does not have value set requirement/ownership: --namespace=openshift-monitoring configmap/metrics-client-ca regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-insights secret/insights-runtime-extractor-tls regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=kube-system configmap/extension-apiserver-authentication regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-apiserver configmap/image-import-ca regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-catalogd configmap/catalogd-trusted-ca-bundle regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-config-managed configmap/image-registry-ca regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-config-managed configmap/merged-trusted-image-registry-ca regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-etcd configmap/etcd-all-bundles regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-image-registry configmap/image-registry-certificates regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-monitoring configmap/metrics-client-ca regressed and does not have value set requirement/autoregenerate-after-expiry: --namespace=openshift-operator-controller configmap/operator-controller-trusted-ca-bundle regressed and does not have value set requirement/descriptions: --namespace=kube-system configmap/extension-apiserver-authentication regressed and does not have value set requirement/descriptions: --namespace=openshift-apiserver configmap/image-import-ca regressed and does not have value set requirement/descriptions: --namespace=openshift-catalogd configmap/catalogd-trusted-ca-bundle regressed and does not have value set requirement/descriptions: --namespace=openshift-config-managed configmap/image-registry-ca regressed and does not have value set requirement/descriptions: --namespace=openshift-etcd configmap/etcd-all-bundles regressed and does not have value set requirement/descriptions: --namespace=openshift-image-registry configmap/image-registry-certificates regressed and does not have value set requirement/descriptions: --namespace=openshift-monitoring configmap/metrics-client-ca regressed and does not have value set requirement/descriptions: --namespace=openshift-operator-controller configmap/operator-controller-trusted-ca-bundle regressed and does not have value set Ginkgo exit error 4: exit with code 4}
Actual results:
Case always ran into flaky.
Expected results:
Case should run passed, all registered tls artifacts must have no metadata violation regressions
- relates to
-
API-1886 CI implementation: Create TLS artifacts registry
-
- Closed
-