Skip to content

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

Merged

Conversation

bfournie
Copy link
Contributor

@bfournie bfournie commented Oct 29, 2024

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.

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low 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 Oct 29, 2024
@openshift-ci-robot
Copy link
Contributor

@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
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zniu1011

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

In response to this:

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 #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.

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 requested a review from zniu1011 October 29, 2024 23:15
@bfournie
Copy link
Contributor Author

/cc @rwsu @zaneb @andfasano

@pawanpinjarkar
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 4, 2024
@bfournie
Copy link
Contributor Author

bfournie commented Nov 4, 2024

/test e2e-agent-ha-dualstack

@zaneb
Copy link
Member

zaneb commented Nov 5, 2024

Does this mean that we had a bigger problem, that the user's proxy settings were never passed on to the cluster??

@bfournie
Copy link
Contributor Author

bfournie commented Nov 5, 2024

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.

Copy link
Member

@zaneb zaneb left a 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.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 5, 2024
Copy link
Contributor

openshift-ci bot commented Nov 5, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed lgtm Indicates that a PR is ready to be merged. labels Nov 5, 2024
@bfournie bfournie force-pushed the agent-rendezvous-noproxy branch from 3b45ee7 to a257953 Compare November 7, 2024 01:52
@zaneb
Copy link
Member

zaneb commented Nov 7, 2024

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 7, 2024
@bfournie bfournie force-pushed the agent-rendezvous-noproxy branch from a257953 to 904b949 Compare November 7, 2024 12:26
@openshift-ci-robot
Copy link
Contributor

@bfournie: This pull request references Jira Issue OCPBUGS-30292, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @zniu1011

In response to this:

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.

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.

@bfournie bfournie force-pushed the agent-rendezvous-noproxy branch from 904b949 to b92a4b0 Compare November 7, 2024 13:37
@bfournie bfournie changed the title OCPBUGS-30292: If agent proxy defined add RendezvousIP to noProxy OCPBUGS-30292: If agent proxy, defined add MachineNetwork to noProxy Nov 8, 2024
@rwsu
Copy link
Contributor

rwsu commented Nov 8, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 8, 2024
@bfournie bfournie changed the title OCPBUGS-30292: If agent proxy, defined add MachineNetwork to noProxy OCPBUGS-30292: If agent proxy defined, add MachineNetwork to noProxy Nov 8, 2024
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.
@bfournie bfournie force-pushed the agent-rendezvous-noproxy branch from b92a4b0 to 52277e5 Compare November 8, 2024 23:17
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 8, 2024
Copy link
Contributor

openshift-ci bot commented Nov 9, 2024

@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.

@rwsu
Copy link
Contributor

rwsu commented Nov 9, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 9, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit c3e9b51 into openshift:master Nov 9, 2024
26 checks passed
@openshift-ci-robot
Copy link
Contributor

@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:

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.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.19.0-202411090336.p0.gc3e9b51.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.19.0-202411090336.p0.gc3e9b51.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.19.0-202411090336.p0.gc3e9b51.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.19.0-202411090336.p0.gc3e9b51.assembly.stream.el9.
All builds following this will include this PR.

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-low Referenced Jira bug's severity is low 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.

6 participants