Skip to content

CNF-20336: Add periodic CI configuration for MetalLB 4.21#74510

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
andreaskaris:metallb-periodics-4.21
Feb 9, 2026
Merged

CNF-20336: Add periodic CI configuration for MetalLB 4.21#74510
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
andreaskaris:metallb-periodics-4.21

Conversation

@andreaskaris
Copy link
Contributor

@andreaskaris andreaskaris commented Feb 6, 2026 •
edited
Loading

Add file:
ci-operator/config/openshift/metallb/
openshift-metallb-release-4.21__periodics.yaml

Run:
make jobs

Signed-off-by: Andreas Karis ak.karis@gmail.com

$ diff ci-operator/config/openshift/metallb/openshift-metallb-release-4.2{0,1}__periodics.yaml
15c15
<       name: "4.20"
---
>       name: "4.21"
40c40
<   branch: release-4.20
---
>   branch: release-4.21

@andreaskaris
Add periodic CI configuration for MetalLB 4.21
36f2c3e 
Add file:
  ci-operator/config/openshift/metallb/\
    openshift-metallb-release-4.21__periodics.yaml

Run:
  make jobs

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
@openshift-ci openshift-ci bot requested review from fedepaol and oribon February 6, 2026 10:59
@andreaskaris
Copy link
Contributor Author

andreaskaris commented Feb 6, 2026

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 6, 2026

@andreaskaris: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@andreaskaris
Copy link
Contributor Author

andreaskaris commented Feb 6, 2026

/pj-rehearse list

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 6, 2026

@andreaskaris: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@andreaskaris andreaskaris changed the title Add periodic CI configuration for MetalLB 4.21 CNF-20336: Add periodic CI configuration for MetalLB 4.21 Feb 6, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 6, 2026 •
edited by openshift-ci bot
Loading

@andreaskaris: This pull request references CNF-20336 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Add file:
ci-operator/config/openshift/metallb/
openshift-metallb-release-4.21__periodics.yaml

Run:
make jobs

Signed-off-by: Andreas Karis ak.karis@gmail.com

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 6, 2026
@andreaskaris
Copy link
Contributor Author

andreaskaris commented Feb 6, 2026

@karampok should pj-rehearse post to team-metallb-ci-periodic when the rehearse job is running? because I'm not seeing anything posted there -- -thanks!

@andreaskaris
Copy link
Contributor Author

andreaskaris commented Feb 9, 2026

/pj-rehearse list

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 9, 2026

@andreaskaris: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 9, 2026

[REHEARSALNOTIFIER]
@andreaskaris: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-metallb-release-4.21-periodics-metallb-e2e-metal-periodic N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 9, 2026 •
edited by openshift-ci bot
Loading

@andreaskaris: This pull request references CNF-20336 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Add file:
ci-operator/config/openshift/metallb/
openshift-metallb-release-4.21__periodics.yaml

Run:
make jobs

Signed-off-by: Andreas Karis ak.karis@gmail.com

$ diff ci-operator/config/openshift/metallb/openshift-metallb-release-4.2{0,1}__periodics.yaml
15c15
<       name: "4.20"
---
>       name: "4.21"
40c40
<   branch: release-4.20
---
>   branch: release-4.21

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.

1 similar comment
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 9, 2026 •
edited by openshift-ci bot
Loading

@andreaskaris: This pull request references CNF-20336 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Add file:
ci-operator/config/openshift/metallb/
openshift-metallb-release-4.21__periodics.yaml

Run:
make jobs

Signed-off-by: Andreas Karis ak.karis@gmail.com

$ diff ci-operator/config/openshift/metallb/openshift-metallb-release-4.2{0,1}__periodics.yaml
15c15
<       name: "4.20"
---
>       name: "4.21"
40c40
<   branch: release-4.20
---
>   branch: release-4.21

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.

@andreaskaris
Copy link
Contributor Author

andreaskaris commented Feb 9, 2026

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 9, 2026

@andreaskaris: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 9, 2026
oribon
oribon reviewed Feb 9, 2026
View reviewed changes
ci-operator/config/openshift/metallb/openshift-metallb-release-4.21__periodics.yaml
image_stream_tag:
name: release
namespace: openshift
tag: rhel-8-release-golang-1.16-openshift-4.9
Copy link
Contributor

@oribon oribon Feb 9, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

why do we need the openshift-4.9 suffix? (the 4.19 and 4.20 files do not have it)
sorry was on a wrong checkout 😛 (and missed your git diff)

/lgtm
/approve

@oribon
Copy link
Contributor

oribon commented Feb 9, 2026

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreaskaris, oribon

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 Feb 9, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit bb666f3 into openshift:master Feb 9, 2026
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fedepaol fedepaol Awaiting requested review from fedepaol

1 more reviewer

@oribon oribon oribon left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@oribon oribon

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@andreaskaris @openshift-ci-robot @oribon