Bug 1986540
| Summary: | Cluster Proxy not used during installation on OSP | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Maysa Macedo <mdemaced> |
| Component: | Cloud Compute | Assignee: | Eric Duen <eduen> |
| Cloud Compute sub component: | OpenStack Provider | QA Contact: | Jon Uriarte <juriarte> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | adduarte, egarcia, emacchi, m.andre, mfedosin, mimccune, pprinett |
| Version: | 4.8 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | 4.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The HTTP transport to connect to OpenStack endpoints using a custom CA certificate was missing the Proxy settings.
Consequence: Cluster wasn't fully operational when deployed on OpenStack with a combination of proxy and custom CA certificate.
Fix: Pass the proxy settings to the HTTP transport used when connecting with a custom CA certificate.
Result: All cluster components work as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-18 17:42:20 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: | 2000542 | ||
|
Description
Maysa Macedo
2021-07-27 18:05:27 UTC
Verified on 4.9.0-0.nightly-2021-08-31-123131 on top of OSP 16.1.6 (RHOS-16.1-RHEL-8-20210604.n.0)
All the operators are available after IPI installation on a restricted network using proxy, and machine-controller container
is not trying to connect to the OSP API outside the proxy (the error message in the description of the BZ is not being shown).
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.9.0-0.nightly-2021-08-31-123131 True False 43h Cluster version is 4.9.0-0.nightly-2021-08-31-123131
$ oc get proxy cluster -o json | jq .status
{
"httpProxy": "http://dummy:dummy@172.16.0.3:3128/",
"httpsProxy": "https://dummy:dummy@172.16.0.3:3130/",
"noProxy": ".cluster.local,.svc,10.128.0.0/14,127.0.0.1,169.254.169.254,172.16.0.0/24,172.30.0.0/16,api-int.ostest.shiftstack.com,localhost"
}
$ oc -n openshift-machine-api get pods
NAME READY STATUS RESTARTS AGE
cluster-autoscaler-operator-76cf8dc889-jfjrj 2/2 Running 0 43h
cluster-baremetal-operator-56fd57cd8d-gzpbt 2/2 Running 0 43h
machine-api-controllers-5865dc5b55-z4d7q 7/7 Running 0 43h
machine-api-operator-594ddf49fb-wd74j 2/2 Running 0 43h
$ oc -n openshift-machine-api -c machine-controller rsh machine-api-controllers-5865dc5b55-z4d7q
sh-4.4$ env | grep -i proxy
HTTP_PROXY=http://dummy:dummy@172.16.0.3:3128/
NO_PROXY=.cluster.local,.svc,10.128.0.0/14,127.0.0.1,169.254.169.254,172.16.0.0/24,172.30.0.0/16,api-int.ostest.shiftstack.com,localhost
HTTPS_PROXY=https://dummy:dummy@172.16.0.3:3130/
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759 |