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

OCPBUGS-44167: Ensure rendezvousIP is checked against host IP #9167

Merged

Conversation

bfournie
Copy link
Contributor

@bfournie bfournie commented Nov 4, 2024

The rendezvousIP is currently checked against any substring in the nmstate configuration which can result in validation failure if the next-hop-address matches the rendezvousIP. Ensure that the check is against the host IP.

@openshift-ci-robot
Copy link
Contributor

@bfournie: No Jira issue with key sOCPBUGS-44167 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

The rendezvousIP is currently checked against any substring in the nmstate configuration which can result in validation failure if the next-hop-address matches the rendezvousIP. Ensure that the check is against the host IP.

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 changed the title sOCPBUGS-44167: Ensure rendezvousIP is checked against host IP OCPBUGS-44167: Ensure rendezvousIP is checked against host IP Nov 4, 2024
@openshift-ci-robot openshift-ci-robot added 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 Nov 4, 2024
@openshift-ci-robot
Copy link
Contributor

@bfournie: This pull request references Jira Issue OCPBUGS-44167, 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 @mhanss

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

In response to this:

The rendezvousIP is currently checked against any substring in the nmstate configuration which can result in validation failure if the next-hop-address matches the rendezvousIP. Ensure that the check is against the host IP.

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 rendezvous-worker-string branch 2 times, most recently from 4b00926 to d2cb13e Compare November 4, 2024 18:04
@bfournie
Copy link
Contributor Author

bfournie commented Nov 4, 2024

/retest

@bfournie bfournie force-pushed the rendezvous-worker-string branch 2 times, most recently from d6bd692 to 0e3a34e Compare November 4, 2024 19:00
@bfournie
Copy link
Contributor Author

bfournie commented Nov 4, 2024

/retest

Copy link
Contributor

@pawanpinjarkar pawanpinjarkar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 5, 2024
The rendezvousIP is currently checked against any substring
in the nmstate configuration which can result in validation
failure if the next-hop-address matches the rendezvousIP.
Ensure that the check is against the host IP.
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 5, 2024
@andfasano
Copy link
Contributor

/approve

Copy link
Contributor

openshift-ci bot commented Nov 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano

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 Nov 5, 2024
@pawanpinjarkar
Copy link
Contributor

/lgtm

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

/retest-required

Remaining retests: 0 against base HEAD c093891 and 2 for PR HEAD 2f10e80 in total

Copy link
Contributor

openshift-ci bot commented Nov 5, 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 24f72f0 into openshift:master Nov 5, 2024
25 checks passed
@openshift-ci-robot
Copy link
Contributor

@bfournie: Jira Issue OCPBUGS-44167: All pull requests linked via external trackers have merged:

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

In response to this:

The rendezvousIP is currently checked against any substring in the nmstate configuration which can result in validation failure if the next-hop-address matches the rendezvousIP. Ensure that the check is against the host IP.

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 deleted the rendezvous-worker-string branch November 5, 2024 21:54
@bfournie
Copy link
Contributor Author

bfournie commented Nov 5, 2024

/cherry-pick release-4.17

@openshift-cherrypick-robot

@bfournie: #9167 failed to apply on top of branch "release-4.17":

Applying: OCPBUGS-44167: Ensure rendezvousIP is checked against host IP
Using index info to reconstruct a base tree...
M	pkg/asset/agent/common.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/asset/agent/common.go
CONFLICT (content): Merge conflict in pkg/asset/agent/common.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OCPBUGS-44167: Ensure rendezvousIP is checked against host IP

In response to this:

/cherry-pick release-4.17

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.

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

5 participants