Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.15] OCPBUGS-27239: [cluster] Keep comma as delimiter in noProxy list #2015

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1998

/assign saifshaikh48

Reverts an erroneous sanitization step in WMCO that replaced commas with
semicolons in the user's cluster-wide proxy configuration. This was
causing Windows to ignore the values set in the noProxy environment variable,
incorrectly sending traffic through the proxy.

From the Azure PowerShell docs:
`NO_PROXY: a comma-separated list of hostnames that should be excluded from proxying.`
`noProxy list should not contain semicolon delimiters (;). Use (,) to delimit the noProxy domains.`
This commit adds a new set of subtests to the proxy suite.
The first ensures that default outbound requests use the proxy variables
and actually are routed through the proxy by investigating curl headers.
The second ensures that hitting an endpoint that is under the NO_PROXY
list does not go through the proxy server.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-24264 has been cloned as Jira Issue OCPBUGS-27239. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-27239: [cluster] Keep comma as delimiter in noProxy list

In response to this:

This is an automated cherry-pick of #1998

/assign saifshaikh48

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.15] OCPBUGS-24264: [cluster] Keep comma as delimiter in noProxy list [release-4.15] OCPBUGS-27239: [cluster] Keep comma as delimiter in noProxy list Jan 16, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 16, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-27239, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-24264 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-24264 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @rrasouli

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #1998

/assign saifshaikh48

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@mansikulkarni96
Copy link
Member

/approve

Copy link
Contributor

openshift-ci bot commented Jan 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mansikulkarni96, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 16, 2024
@saifshaikh48
Copy link
Contributor

/test remaining-required

@saifshaikh48
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c39c7b and 2 for PR HEAD 958c4ec in total

Copy link
Contributor

openshift-ci bot commented Jan 17, 2024

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 5147e86 into openshift:release-4.15 Jan 17, 2024
17 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27239: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27239 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #1998

/assign saifshaikh48

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@mtnbikenc
Copy link
Member

@saifshaikh48 Shouldn't this be backported to release-4.14 next?

@saifshaikh48
Copy link
Contributor

/cherry-pick release-4.14

@mtnbikenc I had created cherry-picked into 4.14 from the master PR, will close that one and open from here

@openshift-cherrypick-robot
Copy link
Author

@saifshaikh48: new pull request created: #2023

In response to this:

/cherry-pick release-4.14

@mtnbikenc I had created cherry-picked into 4.14 from the master PR, will close that one and open from here

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants