Bug 2005095

Summary: Setting an IPv6 address in noProxy field causes error in openshift installer
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Andrey Lebedev <alebedev>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED WONTFIX Docs Contact:
Severity: low    
Priority: medium CC: amcdermo, anbhat, aos-bugs, mfisher, mmasters, ohochman, sasha, tsze, vemporop, yanyang
Version: 4.8   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The cluster-wide proxy configuration could not accept IPv6 addresses for noProxy setting. Consequence: It was not possible to install a cluster whose configuration was having noProxy with IPv6 addresses. Fix: Cluster Network Operator is now able to parse IPv6 addresses for the noProxy setting of the cluster-wide proxy resource. Result: It's now possible to exclude IPv6 addresses from proxying.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-02 01:46:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1939435    
Bug Blocks: 2004793    

Comment 1 Hongan Li 2021-09-17 03:36:53 UTC 
verified with a cluster launched by cluster-bot (launch openshift/cluster-network-operator#1199) and passed

$ oc get clusterversion
NAME      VERSION                                                  AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.ci.test-2021-09-17-014320-ci-ln-f8b9ll2-latest   True        False         80m     Cluster version is 4.9.0-0.ci.test-2021-09-17-014320-ci-ln-f8b9ll2-latest

$ oc get proxies cluster -oyaml
<---snip--->
spec:
  httpProxy: http://user:xxxx@10.0.99.4:3128
  httpsProxy: http://user:xxxx@10.0.99.4:3128
  noProxy: test.no-proxy.com,registry.ocp-edge-cluster-0.qe.lab.redhat.com,ocp-edge-cluster-0.qe.lab.redhat.com,fd2e:6f44:5dd8::1,.ocp-edge-cluster-0.qe.lab.redhat.com
  trustedCA:
    name: ""
status:
  httpProxy: http://user:xxxx@10.0.99.4:3128
  httpsProxy: http://user:xxxx@10.0.99.4:3128
  noProxy: .cluster.local,.ocp-edge-cluster-0.qe.lab.redhat.com,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.ci-ln-f8b9ll2-f76d1.origin-ci-int-gce.dev.openshift.com,fd2e:6f44:5dd8::1,localhost,metadata,metadata.google.internal,metadata.google.internal.,ocp-edge-cluster-0.qe.lab.redhat.com,registry.ocp-edge-cluster-0.qe.lab.redhat.com,test.no-proxy.com

$ oc -n openshift-network-operator logs network-operator-75c685b47d-2s6t9 | grep validate
Comment 6 Miciah Dashiel Butler Masters 2022-11-02 01:46:01 UTC 
This is a low-severity backport bug, no one is clamoring for it to be fixed on 4.9.z, and 4.9.z is fairly old now, so I am closing this BZ as WONTFIX.