Description of problem: Builder/deployment pods are unable to resolve domains, e.g. source S2I builds fail with the following message: Could not resolve host: github.com The issue does not seem to be occuring elsewhere than pods, for example, importing images from remote registries functions. The OCP4.6/4.7 clusters installed with same configuration do not have any issues with resolving domain names. OpenShift release version: 4.8.2, 4.8.3, 4.8.4 Cluster Platform: IPI OpenStack, x86_64 VMs How reproducible: Always Steps to Reproduce (in detail): 1. Install OCP 4.8 cluster on OpenStack with IPI 2. Once cluster is ready, import registry.access.redhat.com/ubi8/openjdk-11:latest cat <<-EOF | ./oc apply -f - apiVersion: image.openshift.io/v1 kind: ImageStream metadata: name: openjdk-11 spec: lookupPolicy: local: false tags: - name: latest from: kind: DockerImage name: registry.access.redhat.com/ubi8/openjdk-11:latest 3. Create source S2I build with the created imagestream: oc new-app openjdk-11 https://github.com/quarkusio/quarkus-quickstarts.git\#1.11 --context-dir=getting-started --name=getting-started Actual results: Build fails as git in build pod is unable to resolve github.com Expected results: Build succeeds Additional info: install-config.yaml apiVersion: v1 baseDomain: ${QUARKUS_QE_DOMAIN} metadata: name: ${OPENSHIFT_CLUSTER_NAME} controlPlane: name: master platform: {} replicas: 3 compute: - name: worker platform: openstack: type: ${OPENSTACK_FLAVOR_COMPUTE} replicas: 3 networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineCIDR: 172.208.0.0/16 networkType: OpenShiftSDN serviceNetwork: - 172.30.0.0/16 platform: openstack: cloud: openstack computeFlavor: ${OPENSTACK_FLAVOR_CONTROL_PLANE} externalDNS: null externalNetwork: ${OPENSTACK_NETWORK} lbFloatingIP: ${OPENSTACK_FLOATING_IP_API} octaviaSupport: "0" region: "regionOne" trunkSupport: "1" publish: External pullSecret: '$(cat ${OPENSHIFT_PULL_SECRET})' sshKey: '$(cat ${OPENSHIFT_SSH_KEY})' ========================= ** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report. You may also mark the bug private if you wish.
Miheer, can you look into the failure to resolve github.com?
Sure Miciah. Just working on to reproduce this issue.
*** This bug has been marked as a duplicate of bug 1991067 ***