Bug 1782829 - The DNS provider failed to ensure the record: caused by: Post https://route53.amazonaws.com/xxx: dial tcp x.x.x.x:443: i/o timeout
Summary: The DNS provider failed to ensure the record: caused by: Post https://route53...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0
Assignee: Daneyon Hansen
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1765044
Blocks: 1768847
TreeView+ depends on / blocked
 
Reported: 2019-12-12 13:00 UTC by Dan Mace
Modified: 2022-08-04 22:27 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1765044
Environment:
Last Closed: 2020-01-23 11:18:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 340 0 None closed [release-4.3] Bug 1782829: Adds proxy support to ingress operator 2020-11-25 09:20:54 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:14 UTC

Comment 3 Daneyon Hansen 2019-12-13 17:41:15 UTC
That makes sense. Thank you!

Comment 6 Johnny Liu 2019-12-19 11:32:04 UTC
Verified this bug with 4.3.0-0.nightly-2019-12-18-224446, and PASS.

Trigger an install on aws behind proxy, succeed.

# oc get dnsrecords.ingress.operator.openshift.io -o yaml -n openshift-ingress-operator
apiVersion: v1
items:
- apiVersion: ingress.operator.openshift.io/v1
  kind: DNSRecord
  metadata:
    creationTimestamp: "2019-12-19T09:26:22Z"
    finalizers:
    - operator.openshift.io/ingress-dns
    generation: 1
    labels:
      ingresscontroller.operator.openshift.io/owning-ingresscontroller: default
    name: default-wildcard
    namespace: openshift-ingress-operator
    ownerReferences:
    - apiVersion: operator.openshift.io/v1
      blockOwnerDeletion: true
      controller: true
      kind: IngressController
      name: default
      uid: 3e74d28c-6ef9-402b-98d5-75af69215e87
    resourceVersion: "9101"
    selfLink: /apis/ingress.operator.openshift.io/v1/namespaces/openshift-ingress-operator/dnsrecords/default-wildcard
    uid: 29b1ffa7-5744-4f2a-88e8-fddb5ed3060d
  spec:
    dnsName: '*.apps.jialiu43awsbz1.qe.devcluster.openshift.com.'
    recordTTL: 30
    recordType: CNAME
    targets:
    - a7ab1d9ee07674b44b4b9210c23dca47-36094194.us-east-2.elb.amazonaws.com
  status:
    zones:
    - dnsZone:
        tags:
          Name: jialiu43awsbz1-8ll74-int
          kubernetes.io/cluster/jialiu43awsbz1-8ll74: owned
    - dnsZone:
        id: Z3B3KOVA3TRCWP
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""


# oc -n openshift-ingress-operator exec ingress-operator-744b944985-brh4l -- env | grep -i proxy
Defaulting container name to ingress-operator.
Use 'oc describe pod/ingress-operator-744b944985-brh4l -n openshift-ingress-operator' to see all of the containers in this pod.
HTTP_PROXY=http://ec2-18-222-23-12.us-east-2.compute.amazonaws.com:3128
HTTPS_PROXY=http://ec2-18-222-23-12.us-east-2.compute.amazonaws.com:3128
NO_PROXY=.cluster.local,.svc,.us-east-2.compute.internal,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.jialiu43awsbz1.qe.devcluster.openshift.com,etcd-0.jialiu43awsbz1.qe.devcluster.openshift.com,etcd-1.jialiu43awsbz1.qe.devcluster.openshift.com,etcd-2.jialiu43awsbz1.qe.devcluster.openshift.com,localhost,test.no-proxy.com

Comment 8 errata-xmlrpc 2020-01-23 11:18:56 UTC
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:0062


Note You need to log in before you can comment on or make changes to this bug.