Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #113

/assign oribon

Now that we have a new process to bump rpms,
we remove the temporary pinning that was set in place
to avoid scenarios where the latest rpm breaks

Signed-off-by: Ori Braunshtein <obraunsh@redhat.com>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-66055 has been cloned as Jira Issue OCPBUGS-74485. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-74485: Dockerfile: unpin FRR rpm

Details

In response to this:

This is an automated cherry-pick of #113

/assign oribon

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.18] OCPBUGS-66055: Dockerfile: unpin FRR rpm [release-4.18] OCPBUGS-74485: Dockerfile: unpin FRR rpm Jan 27, 2026
@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 Jan 27, 2026
@openshift-ci-robot
Copy link

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

  • expected dependent Jira Issue OCPBUGS-66055 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.

Details

In response to this:

This is an automated cherry-pick of #113

/assign oribon

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 requested review from cgoncalves and fedepaol January 27, 2026 09:01
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign dougbtv for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@oribon
Copy link
Contributor

oribon commented Jan 27, 2026

/retest-required

1 similar comment
@oribon
Copy link
Contributor

oribon commented Jan 28, 2026

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 28, 2026

@openshift-cherrypick-robot: 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/security 90006ed link false /test security
ci/prow/frrk8s-e2e-metal 90006ed link true /test frrk8s-e2e-metal

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants