-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.17.0
-
None
-
Critical
-
None
-
5
-
False
-
-
Release Note Not Required
-
In Progress
seeing various MCO issue across different platforms and repos on techpreview
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_clus[…]der-aws-master-e2e-aws-ovn-techpreview/1818614625273384960
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_clus[…]der-aws-master-e2e-aws-ovn-techpreview/1818592543001022464
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_clus[…]perator-main-e2e-azure-ovn-techpreview/1818562032329297920
- https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_clus[…]perator-main-e2e-azure-ovn-techpreview/1818592686244892672
@David Joshy found that it might be https://github.com/openshift/cluster-update-keys/pull/58
@jerzhang found diffs in sigstore-registries and policy.json. Which may be coming from this manifest. Is this available during bootstrap?
- blocks
-
OCPBUGS-38257 techpreview cluster image policy generator mismatch on bootstrap vs runtime - breaking installs
- Closed
- is cloned by
-
OCPBUGS-38257 techpreview cluster image policy generator mismatch on bootstrap vs runtime - breaking installs
- Closed
- links to
(2 links to)