Loading...

XML

Word

Printable

Release Note Status:
Done
Release Note Type:
Bug Fix
Release Note Text:

Hide
When a Proxy is configured the installer adds the machineNetwork CIDR to the noProxy field. If the machineNetwork CIDR had also been configured by the user in noProxy this will result in a duplicate entry, which is not allowed by ignition and could prevent the host from booting properly. This fix ensures that the installer will not add the machineNetwork CIDR to noProxy if it has already been set.

Show
When a Proxy is configured the installer adds the machineNetwork CIDR to the noProxy field. If the machineNetwork CIDR had also been configured by the user in noProxy this will result in a duplicate entry, which is not allowed by ignition and could prevent the host from booting properly. This fix ensures that the installer will not add the machineNetwork CIDR to noProxy if it has already been set.

This is a clone of issue ~~OCPBUGS-53183~~. The following is the description of the original issue:
—
Description of problem:

In https://github.com/openshift/installer/pull/9153, the MachineNetwork was added to NO_PROXY when a proxy was defined in order to ensure that the the rendezvous IP could be reached by other masters. However if that network was already in the NO_PROXY it can cause problems, the assisted-service has a validation to check this, see https://github.com/openshift/assisted-service/pull/7305.

Before the MachineNetwork is added there should be a check to ensure its not a duplicate.

clones

OCPBUGS-53183 Agent installer should not add duplicate NO_PROXY entry

is blocked by

OCPBUGS-53183 Agent installer should not add duplicate NO_PROXY entry

links to

RHBA-2025:3293 OpenShift Container Platform 4.18.z bug fix update