Description of problem: The pull secret for the internal registry associated with each service account includes the ClusterIP address of the registry service. This is invalid if the cluster is using IPv6 addresses. Version-Release number of selected component (if applicable): 4.3.0 How reproducible: Always Steps to Reproduce: 1. Deploy OCP in an IPv6 cluster 2. Create a project 3. Decode the dockercfg secret associated with the project's default and builder service accounts Actual results: Pull secret includes a registry location that has an IPv6 address. Expected results: Pull secret should not have IPv6 address locations. IPv6 addresses are not supported locations in an image pull spec. Additional info:
Target 4.4.0. Per eparis will need a backport to 4.3.z.
I successfully tested this change
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. https://access.redhat.com/errata/RHBA-2020:0581