"no-proxy" is not automatically set when setting docker proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
João Victor Portal |
Bug Description
Brief Description
-----------------
"no-proxy" is not automatically set when setting docker proxy. One symptom is pods failing, like ceph-pools-audit (executed every 5 minutes), because the pod executes a request using the Kubernetes apiserver cluster API IP (10.96.0.1 in IPv4 deploys) and this request is sent to the proxy, while it should be treated locally (the IP 10.96.0.1 should be present in the environment variable "NO_PROXY" of docker and containerd services).
Severity
--------
Major.
Steps to Reproduce
------------------
Set up proxy with
source /etc/platform/
system service-
system service-
system service-
Expected Behavior
------------------
Proxy is applied, rest of the functionalities is not impacted.
Actual Behavior
----------------
Since "no-proxy" is not automatically configured with proxy setting, the functionality gets broken.
Reproducibility
---------------
100% reproducible.
System Configuration
-------
Any.
Branch/Pull Time/Commit
-------
NA.
Last Pass
---------
NA.
Timestamp/Logs
--------------
NA.
Test Activity
-------------
NA.
Workaround
----------
Manually set up "no-proxy".
Changed in starlingx: | |
assignee: | nobody → João Victor Portal (jvictorp) |
Changed in starlingx: | |
status: | New → In Progress |
description: | updated |
description: | updated |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.10.0 stx.containers |
Changed in starlingx: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. opendev. org/c/starlingx /docs/+ /916834
Review: https:/