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.

Sign up for GitHub

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

Jump to bottom

[release-4.15] OCPBUGS-32972: Deploy dual stack with IPv6 on top of bond/vlan fails #6245

Open
wants to merge 1 commit into
base: release-4.15
Choose a base branch
from
Open

[release-4.15] OCPBUGS-32972: Deploy dual stack with IPv6 on top of bond/vlan fails #6245

wants to merge 1 commit into from

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #6149

/assign bfournie

@ori-amizur
OCPBUGS-31631: Deploy dual stack with IPv6 on top of bond/vlan fails
b7bc0b9 
IPv6 L2 connectivity check uses nmap.  nmap uses NDP (Network Discovery
Protocol) to check L2 connectivty to IPv6 hosts. There are cases that
NDP response does not arrive or it is not captured by nmap which means
that the system assumes there is no connectivity to the host.  However,
there might be L3 connectivity (ping) to the same host.
So change adds fallback for IPv6 L2 connectivity.  In case there is
failure in L2 connectivity to IPv6 host and success in L3 connecivity to
the same host, the host is assumed connected on L2, providing that the
remote address is part of the L2 subnet being checked.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 25, 2024
Merged
20 tasks
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-31631 has been cloned as Jira Issue OCPBUGS-32972. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-32972: Deploy dual stack with IPv6 on top of bond/vlan fails

In response to this:

This is an automated cherry-pick of #6149

/assign bfournie

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-31631: Deploy dual stack with IPv6 on top of bond/vlan fails [release-4.15] OCPBUGS-32972: Deploy dual stack with IPv6 on top of bond/vlan fails Apr 25, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 25, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-32972, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
  • expected dependent Jira Issue OCPBUGS-31631 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

/assign bfournie

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 added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 25, 2024
@openshift-ci openshift-ci bot requested review from avishayt and omertuc April 25, 2024 12:47
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 25, 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.

@ori-amizur
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 25, 2024
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@avishayt avishayt Awaiting requested review from avishayt

@omertuc omertuc Awaiting requested review from omertuc

Assignees

@bfournie bfournie

@ori-amizur ori-amizur

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@openshift-cherrypick-robot @openshift-ci-robot @ori-amizur @bfournie