Description of problem:
There is no image-registry manifest in 4.0.0-0.nightly-2019-01-08-152529 payload
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.oc adm release extract registry.svc.ci.openshift.org/ocp/release@sha256:de71c95dbce7a6e284e719a86140a7914ce2e82a2db1607810d3300d989f8d4c --to=.
No image-registry manifest.
If no image-registry operator manifest, internal image-registry cannot be setup. Build won't succeed for pushing built image to.
Who's in charge of OCP builds? I don't think it's Alex or me. Do we have a better Component for OCP build issues, since this isn't an installer issue?
Tim Bielawa suggests the "Release" component for issues with the OCP update payloads. I'm not authorized to update this bug myself, but maybe you can fix the Component field, Wenjing?
Verified with 4.0.0-0.nightly-2019-01-12-000105 as below:
$ oc adm release extract --from=registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-01-12-000105 --to=.
$ ls | grep registry
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.