I saw the `Target Release` is 4.3.0 , but other similar issue like https://bugzilla.redhat.com/show_bug.cgi?id=1790442 ,its `Target Release` is 4.3.z, and the ipv6 issue can't be verified with the 4.3.0 errata, is this right ?
Assigning all 4.3.z IPv6 bugs to Marius Cornea for QA, as they are not yet QA-able in stock release-4.3 builds.
Verified on 4.3.0-0.nightly-2020-02-10-055634(included in 4.3.0-0.nightly-2020-02-10-055634-ipv6.3) on a bare metal deployment
Image used in local disconnected registry:
[kni@provisionhost-0 ~]$ oc adm release info --image-for=cluster-kube-controller-manager-operator -a ~/combined-secret.json registry.ocp-edge-cluster.qe.lab.redhat.com:5000/localimages/local-release-image:4.3.0-0.nightly-2020-02-10-055634-ipv6.3
Image used in 4.3.0-0.nightly-2020-02-10-055634:
[kni@provisionhost-0 ~]$ oc adm release info --image-for=cluster-kube-controller-manager-operator -a ~/combined-secret.json registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2020-02-10-055634
oc -n openshift-monitoring port-forward svc/prometheus-operated 9090
curl -s http://localhost:9090/targets | grep openshift-kube-controller-manager-operator/kube-controller-manager-operator/0
<a id="job-openshift-kube-controller-manager-operator/kube-controller-manager-operator/0" href="#job-openshift-kube-controller-manager-operator%2fkube-controller-manager-operator%2f0">openshift-kube-controller-manager-operator/kube-controller-manager-operator/0 (1/1 up)</a>
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.