-
Bug
-
Resolution: Unresolved
-
Critical
-
4.16, 4.17, 4.18, 4.19
-
Critical
-
None
-
Proposed
-
False
-
-
The pod that perform in-place upgrades will honor the cluster proxy settings now.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-48540. The following is the description of the original issue:
—
Description of problem:
Proxy variables are not respected in the machine config daemon pods when the upgrade strategy is set to inPlace
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Always
Steps to Reproduce:
Create a HCP cluster with the proxy variables defined in `spec.configuration` section.
Â
configuration: proxy: httpProxy: 'http://xx.xx.xx.xx:8080' httpsProxy: 'http://xx.xx.xx:8080' noProxy: 'xx.xx.xx.xx/16,kubernetes,localhost' trustedCA: name: ''
Â
Try upgrading the cluster and when the machine config daemon pod starts in fails to pull the image from the quay registry.
- blocks
-
OCPBUGS-57432 Proxy variables are not passed to machine config daemon pods when upgrade strategy is set to inPlace
-
- Verified
-
- clones
-
OCPBUGS-48540 Proxy variables are not passed to machine config daemon pods when upgrade strategy is set to inPlace
-
- Closed
-
- is blocked by
-
OCPBUGS-48540 Proxy variables are not passed to machine config daemon pods when upgrade strategy is set to inPlace
-
- Closed
-
- is cloned by
-
OCPBUGS-57432 Proxy variables are not passed to machine config daemon pods when upgrade strategy is set to inPlace
-
- Verified
-
- links to
-
RHBA-2025:9269 OpenShift Container Platform 4.18.18 bug fix update