Bug 1783259 - Insights operator unable to resolve cloud.redhat.com with Kuryr
Summary: Insights operator unable to resolve cloud.redhat.com with Kuryr
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: All
OS: All
low
low
Target Milestone: ---
: 4.3.0
Assignee: Luis Tomas Bolivar
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On: 1754046
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-13 13:08 UTC by Luis Tomas Bolivar
Modified: 2020-01-23 11:19 UTC (History)
7 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 425 0 None closed [release-4.3] Bug 1783259: Modif kuryr-admission-controller pod definition 2020-04-20 18:32:38 UTC
Github openshift kuryr-kubernetes pull 110 0 None closed [release-4.3] Bug 1783259: Ensure kuryr webhook is running before other operators' pods 2020-04-20 18:32:38 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:49 UTC

Comment 2 Jon Uriarte 2019-12-24 10:52:28 UTC
Verified in 4.3.0-0.nightly-2019-12-23-120031 on 2019-12-06.2 OSP 13 puddle.

The OCP installer finishes successfully:

 $ oc get clusterversion
 NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
 version   4.3.0-0.nightly-2019-12-23-120031   True        False         13h     Cluster version is 4.3.0-0.nightly-2019-12-23-120031

insights-operator is newer then the kuryr-dns-admission-controller pods, as now insights-operator is restarted once the admission controller
is ready, so it can be configured to use TCP instead of UDP for DNS resolution.

 $ oc get pods -A
 NAMESPACE             NAME                                  READY   STATUS      RESTARTS   AGE
 openshift-insights    insights-operator-64559cfc5d-m9kk4    1/1     Running     3          16h
 openshift-kuryr       kuryr-dns-admission-controller-5jggg  1/1     Running     0          16h
 openshift-kuryr       kuryr-dns-admission-controller-grb46  1/1     Running     0          16h
 openshift-kuryr       kuryr-dns-admission-controller-qrrd9  1/1     Running     0          16h

 $ oc -n openshift-insights describe pod insights-operator-64559cfc5d-m9kk4 | grep Started
      Started:   Mon, 23 Dec 2019 13:44:46 -0500
      Started:      Mon, 23 Dec 2019 13:40:19 -0500

 $ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-5jggg | grep Started
      Started:      Mon, 23 Dec 2019 13:17:32 -0500

 $ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-grb46 | grep Started
      Started:      Mon, 23 Dec 2019 13:15:37 -0500

 $ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-qrrd9 | grep Started
      Started:      Mon, 23 Dec 2019 13:17:32 -0500

insights-operator is not showing error messages either.

Comment 3 Jon Uriarte 2019-12-24 11:00:38 UTC
Adding more info:

$ oc -n openshift-insights get pod insights-operator-64559cfc5d-m9kk4 -o yaml | grep -A3 dnsConfig
  dnsConfig:
    options:
    - name: use-vc
      value: ""

Comment 5 errata-xmlrpc 2020-01-23 11:19:25 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.