Skip to content

[release-4.13] OCPBUGS-15496: Fix default GW IPs retrieval#1738

Merged
openshift-merge-robot merged 3 commits intoopenshift:release-4.13from
kyrtapz:invalix_next_hops_413
Aug 3, 2023
Merged

[release-4.13] OCPBUGS-15496: Fix default GW IPs retrieval#1738
openshift-merge-robot merged 3 commits intoopenshift:release-4.13from
kyrtapz:invalix_next_hops_413

Conversation

@kyrtapz
Copy link
Contributor

@kyrtapz kyrtapz commented Jul 4, 2023

Backport of ovn-kubernetes/ovn-kubernetes#3570
There were conflicts in go-controller/pkg/node/helper_linux.go

kyrtapz added 3 commits July 4, 2023 14:43
…ual-stack cluster

Previously it was allowed to have the IPv6 default GW without having the IPv4 one, we should allow the same in the oposite scenario.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
(cherry picked from commit 1fbcc39)
Only add the gw IP if it is not empty, the previous approach resulted in adding a `<nil>` IP when there was no default GW:
  next-hops":["<nil>","fe80::5054:ff:fedf:631e"]

Signed-off-by: Patryk Diak <pdiak@redhat.com>
(cherry picked from commit e70b35b)
…tewayInterfaceDetails

This commit additionally refactors getDefaultGatewayInterfaceDetails to make it independent of the global config.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
(cherry picked from commit 03ea2c4)
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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 Jul 4, 2023
@openshift-ci-robot
Copy link
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-15496, which is invalid:

  • expected the bug to target the "4.13.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-15496 to depend on a bug targeting a version in 4.14.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

Details

In response to this:

Backport of ovn-kubernetes/ovn-kubernetes#3570
There was one conflict in go-controller/pkg/node/helper_linux.go

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.

@kyrtapz
Copy link
Contributor Author

kyrtapz commented Jul 4, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-15496, which is invalid:

  • expected Jira Issue OCPBUGS-15496 to depend on a bug targeting a version in 4.14.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

Details

In response to this:

/jira refresh

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.

@openshift-ci openshift-ci bot requested review from abhat and dcbw July 4, 2023 13:19
@kyrtapz
Copy link
Contributor Author

kyrtapz commented Jul 4, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-15496, which is invalid:

  • expected dependent Jira Issue OCPBUGS-7875 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead
  • expected dependent Jira Issue OCPBUGS-7875 to target a version in 4.14.0, but no target version was set

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.

Details

In response to this:

/jira refresh

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.

@openshift-ci-robot
Copy link
Contributor

@kyrtapz: This pull request references Jira Issue OCPBUGS-15496, which is invalid:

  • expected dependent Jira Issue OCPBUGS-7875 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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.

Details

In response to this:

Backport of ovn-kubernetes/ovn-kubernetes#3570
There were conflicts in go-controller/pkg/node/helper_linux.go

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 4, 2023

@kyrtapz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openstack-ovn b332d91 link false /test e2e-openstack-ovn
ci/prow/e2e-vsphere-ovn b332d91 link false /test e2e-vsphere-ovn

Full PR test history. Your PR dashboard.

Details

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.

@jcaamano
Copy link
Contributor

jcaamano commented Jul 5, 2023

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 5, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 5, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, kyrtapz

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

The pull request process is described here

Details 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 Jul 5, 2023
@asood-rh
Copy link
Contributor

asood-rh commented Jul 5, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jul 5, 2023
@kyrtapz
Copy link
Contributor Author

kyrtapz commented Jul 11, 2023

/retest-required

@rbbratta
Copy link
Contributor

rbbratta commented Aug 2, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 2, 2023
@openshift-ci-robot
Copy link
Contributor

@rbbratta: This pull request references Jira Issue OCPBUGS-15496, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-7875 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-7875 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @rbbratta

Details

In response to this:

/jira refresh

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.

@openshift-ci openshift-ci bot requested a review from rbbratta August 2, 2023 14:17
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD a7e2297 and 2 for PR HEAD b332d91 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2be24c3 and 1 for PR HEAD b332d91 in total

@openshift-merge-robot openshift-merge-robot merged commit b1774d7 into openshift:release-4.13 Aug 3, 2023
@openshift-ci-robot
Copy link
Contributor

@kyrtapz: Jira Issue OCPBUGS-15496: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Backport of ovn-kubernetes/ovn-kubernetes#3570
There were conflicts in go-controller/pkg/node/helper_linux.go

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.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.13.0-0.nightly-2023-08-03-045759

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-critical Referenced Jira bug's severity is critical 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.