-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.13.0
-
None
-
No
-
False
-
spec.nodeName can be an FQDN whereas HOSTNAME can be the short name. For example, on AWS:
[akaris@linux whereabouts-clusterbot]$ oc rsh -n openshift-multus whereabouts-reconciler-nq49z sh-4.4# env | grep NAME HOSTNAME=ip-10-0-252-190 OPENSHIFT_BUILD_NAME=multus-whereabouts-ipam-cni OPENSHIFT_BUILD_NAMESPACE=ci-ln-d4sindb-1
[akaris@linux whereabouts-clusterbot]$ oc get pods -n openshift-multus whereabouts-reconciler-nq49z -o yaml | grep nodeName nodeName: ip-10-0-252-190.us-west-2.compute.internal
Meaning that this filter expression here fails:
whereabouts-cni/cmd/controlloop/controlloop.go 135 ipPoolInformerFactory := wbinformers.NewSharedInformerFactory(wbClientSet, noResyncPeriod) 136 netAttachDefInformerFactory := nadinformers.NewSharedInformerFactory(nadK8sClientSet, noResyncPeriod) 137 podInformerFactory := v1coreinformerfactory.NewSharedInformerFactoryWithOptions( 138 k8sClientSet, noResyncPeriod, v1coreinformerfactory.WithTweakListOptions( 139 func(options *v1.ListOptions) { 140 const ( 141 filterKey = "spec.nodeName" 142 hostnameEnvVariable = "HOSTNAME" 143 ) 144 options.FieldSelector = fields.OneTermEqualSelector(filterKey, os.Getenv(hostnameEnvVariable)).String() 145 }))
- clones
-
OCPBUGS-10364 new whereabouts reconciler relies on HOSTNAME which != spec.nodeName
- Closed
- depends on
-
OCPBUGS-10364 new whereabouts reconciler relies on HOSTNAME which != spec.nodeName
- Closed
- links to