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-18985: FRR templates: provide a seqnum for the prefix lists #142

Merged

Conversation

fedepaol
Copy link
Member

Instead of letting frr pick the sequence number, we provide it from outside. This should make the configuration more deterministic and offload some of the logic from FRR.

Instead of letting frr pick the sequence number, we provide it from
outside. This should make the configuration more deterministic and
offload some of the logic from FRR.

Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
@openshift-ci
Copy link

openshift-ci bot commented Sep 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fedepaol

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 Sep 14, 2023
@fedepaol
Copy link
Member Author

/jira cherry-pick OCPBUGS-18960

@fedepaol
Copy link
Member Author

/jira cherrypick OCPBUGS-18960

@openshift-ci-robot
Copy link

@fedepaol: Jira Issue OCPBUGS-18960 has been cloned as Jira Issue OCPBUGS-18985. Will retitle bug to link to clone.
/retitle OCPBUGS-18985: FRR templates: provide a seqnum for the prefix lists

In response to this:

/jira cherrypick OCPBUGS-18960

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 changed the title FRR templates: provide a seqnum for the prefix lists OCPBUGS-18985: FRR templates: provide a seqnum for the prefix lists Sep 14, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 14, 2023
@openshift-ci-robot
Copy link

@fedepaol: This pull request references Jira Issue OCPBUGS-18985, which is invalid:

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:

Instead of letting frr pick the sequence number, we provide it from outside. This should make the configuration more deterministic and offload some of the logic from FRR.

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 14, 2023
@fedepaol
Copy link
Member Author

/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 Sep 14, 2023
@fedepaol
Copy link
Member Author

/retest

@fedepaol
Copy link
Member Author

/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 Sep 14, 2023
@openshift-ci-robot
Copy link

@fedepaol: This pull request references Jira Issue OCPBUGS-18985, which is valid. The bug has been moved to the POST state.

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 New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-18960 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-18960 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 @asood-rh

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.

@cgoncalves
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 14, 2023
@gkopels
Copy link

gkopels commented Sep 14, 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 Sep 14, 2023
@openshift-ci
Copy link

openshift-ci bot commented Sep 14, 2023

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

@openshift-merge-robot openshift-merge-robot merged commit d3c8a0d into openshift:release-4.13 Sep 14, 2023
@openshift-ci-robot
Copy link

@fedepaol: Jira Issue OCPBUGS-18985: All pull requests linked via external trackers have merged:

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

In response to this:

Instead of letting frr pick the sequence number, we provide it from outside. This should make the configuration more deterministic and offload some of the logic from FRR.

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.

@fedepaol
Copy link
Member Author

/cherry-pick release-4.12

@openshift-cherrypick-robot

@fedepaol: #142 failed to apply on top of branch "release-4.12":

Applying: FRR templates: provide a seqnum for the prefix lists
Using index info to reconstruct a base tree...
M	internal/bgp/frr/config.go
M	internal/bgp/frr/templates/filters.tmpl
A	internal/bgp/frr/testdata/TestSingleAdvertisementChangeVRF.golden
A	internal/bgp/frr/testdata/TestSingleAdvertisementVRF.golden
A	internal/bgp/frr/testdata/TestSingleAdvertisementWithPeerSelectorVRF.golden
A	internal/bgp/frr/testdata/TestSingleVRFIBGPSession.golden
A	internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsOneVRF.golden
A	internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsOneWithPeerSelectorAndVRF.golden
A	internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsVRFWithPeerSelector.golden
A	internal/bgp/frr/testdata/TestTwoAdvertisementsVRF.golden
A	internal/bgp/frr/testdata/TestTwoSessionsOneVRF.golden
A	internal/bgp/frr/testdata/TestTwoSessionsSameIPRouterIDASNVRF.golden
A	internal/bgp/frr/testdata/TestTwoSessionsSameIPVRF.golden
A	internal/bgp/frr/testdata/TestVRFSingleEBGPSessionMultiHop.golden
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoSessionsSameIPVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoSessionsSameIPVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoSessionsSameIPRouterIDASNVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoSessionsSameIPRouterIDASNVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoSessionsOneVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoSessionsOneVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoAdvertisementsVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoAdvertisementsVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsVRFWithPeerSelector.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsVRFWithPeerSelector.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsOneWithPeerSelectorAndVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsOneWithPeerSelectorAndVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsOneVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestTwoAdvertisementsTwoSessionsOneVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestSingleVRFIBGPSession.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestSingleVRFIBGPSession.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestSingleAdvertisementWithPeerSelectorVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestSingleAdvertisementWithPeerSelectorVRF.golden left in tree.
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestSingleAdvertisementVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestSingleAdvertisementVRF.golden left in tree.
Auto-merging internal/bgp/frr/testdata/TestSingleAdvertisementInvalidPrefix.golden
CONFLICT (content): Merge conflict in internal/bgp/frr/testdata/TestSingleAdvertisementInvalidPrefix.golden
CONFLICT (modify/delete): internal/bgp/frr/testdata/TestSingleAdvertisementChangeVRF.golden deleted in HEAD and modified in FRR templates: provide a seqnum for the prefix lists. Version FRR templates: provide a seqnum for the prefix lists of internal/bgp/frr/testdata/TestSingleAdvertisementChangeVRF.golden left in tree.
Auto-merging internal/bgp/frr/templates/filters.tmpl
CONFLICT (content): Merge conflict in internal/bgp/frr/templates/filters.tmpl
Auto-merging internal/bgp/frr/config.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 FRR templates: provide a seqnum for the prefix lists
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.12

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.

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

7 participants