-
Notifications
You must be signed in to change notification settings - Fork 1.4k
OCPBUGS-30292: If agent proxy defined, add MachineNetwork to noProxy #9153
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
OCPBUGS-30292: If agent proxy defined, add MachineNetwork to noProxy #9153
Conversation
@bfournie: This pull request references Jira Issue OCPBUGS-30292, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/cc @rwsu @zaneb @andfasano |
6962e53
to
b5b2cae
Compare
/lgtm |
/test e2e-agent-ha-dualstack |
Does this mean that we had a bigger problem, that the user's proxy settings were never passed on to the cluster?? |
No, the proxy settings were passed fine to the cluster and to the assisted-installer. Its just that updating the noProxy directly in 10_default.conf.env did not forward the updated noproxy to the assisted installer container. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/hold
Holding so you can look into the Machine CIDR vs. Rendezvous IP question.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zaneb 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 |
3b45ee7
to
a257953
Compare
/hold cancel |
a257953
to
904b949
Compare
@bfournie: This pull request references Jira Issue OCPBUGS-30292, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
904b949
to
b92a4b0
Compare
/lgtm |
If proxy is defined in install-config, add the RendezvousIP to the noproxy field in the generated manifests to ensure the Rendezvous host can be accessed. This is an additional fix beyond openshift#9083 as it was found that when just setting the IP in 10-default-env.conf it did not get passed to the assisted-installer when it was started.
b92a4b0
to
52277e5
Compare
@bfournie: 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-sigs/prow repository. I understand the commands that are listed here. |
/lgtm |
@bfournie: Jira Issue OCPBUGS-30292: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-30292 has been moved to the MODIFIED state. In response to this:
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. |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-terraform-providers |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-altinfra |
[ART PR BUILD NOTIFIER] Distgit: ose-baremetal-installer |
[ART PR BUILD NOTIFIER] Distgit: ose-installer-artifacts |
If proxy is defined in install-config, add the MachineNetwork that contains the RendezvousIP to the noproxy field in the generated manifests to ensure the Rendezvous host can be accessed.
This is an additional fix beyond #9083 as it was found that when just setting the IP in 10-default-env.conf it did not get passed to the assisted-installer when it was started.