Hmm. PR landed 8h ago [1], but the most recent 4.2 nightly is 12h old [2,3]. And, unsurprisingly given its age, that release does not include the network-operator change: $ oc adm release info --commits registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-10-30-152749 | grep network-operator cluster-network-operator https://github.com/openshift/cluster-network-operator 1eed8132527076b9ffca3dc244001a39855f1545 Why did this get swept into ON_QA? Moving back to MODIFIED. [1]: https://github.com/openshift/cluster-network-operator/pull/334#event-2757589099 [2]: https://openshift-release.svc.ci.openshift.org/#4.2.0-0.nightly [3]: https://openshift-release.svc.ci.openshift.org/releasestream/4.2.0-0.nightly/release/4.2.0-0.nightly-2019-10-30-152749
Why did this get moved back to ASSIGNED? Restoring api. was intentional, see [1] and bug 1766066. Did you see something different you didn't like? [1]: https://github.com/openshift/installer/pull/2640
Eric Paris found in BZ https://bugzilla.redhat.com/show_bug.cgi?id=1762618 that at least some of our code, running on cluster, was accessing the external instead of internal api. For the time being, the api external url will be no proxied.