Bug 1754046
| Summary: | Insights operator unable to resolve cloud.redhat.com with Kuryr | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Michał Dulko <mdulko> | |
| Component: | Networking | Assignee: | Luis Tomas Bolivar <ltomasbo> | |
| Networking sub component: | kuryr | QA Contact: | Jon Uriarte <juriarte> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | low | |||
| Priority: | low | CC: | bbennett, eduen, juriarte, ltomasbo, nagrawal | |
| Version: | 4.3.0 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.4.0 | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1783259 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-04 11:13:57 UTC | Type: | Bug | |
| 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: | ||||
| Bug Blocks: | 1783259 | |||
|
Description
Michał Dulko
2019-09-20 16:17:54 UTC
Moved to 4.3. We can backport a fix into 4.2.z if appropriate. Hi Michal, is this a 4.3 blocker bug? I don't think it should be a blocker - we don't really have a feasible solution in close perspective and there is a workaround - just delete problematic pod and it will be fine once recreated. Verified in 4.4.0-0.nightly-2019-12-20-210709 on 2019-12-13.1 OSP 13 puddle.
The OCP installer finishes successfully:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.4.0-0.nightly-2019-12-20-210709 True False 14h Cluster version is 4.4.0-0.nightly-2019-12-20-210709
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-796d568d96-9jrt5 1/1 Running 2 17h
openshift-kuryr kuryr-dns-admission-controller-bjz5b 1/1 Running 0 17h
openshift-kuryr kuryr-dns-admission-controller-r5jmk 1/1 Running 0 17h
openshift-kuryr kuryr-dns-admission-controller-t77dt 1/1 Running 0 17h
$ oc -n openshift-insights describe pod insights-operator-796d568d96-9jrt5 | grep Started
Started: Mon, 23 Dec 2019 12:40:06 -0500
Started: Mon, 23 Dec 2019 12:30:26 -0500
$ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-bjz5b | grep Started
Started: Mon, 23 Dec 2019 12:22:20 -0500
$ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-r5jmk | grep Started
Started: Mon, 23 Dec 2019 12:20:29 -0500
$ oc -n openshift-kuryr describe pod kuryr-dns-admission-controller-t77dt | grep Started
Started: Mon, 23 Dec 2019 12:22:56 -0500
insights-operator is not showing error messages either.
Adding more info:
$ oc -n openshift-insights get pod insights-operator-796d568d96-9jrt5 -o yaml | grep -A3 dnsConfig
dnsConfig:
options:
- name: use-vc
value: ""
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:0581 |