Dockerfile: unpin FRR rpm#110
Conversation
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>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oribon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/lgtm (one day we should change the yum to dnf only btw) |
|
/lgtm |
|
/verified later @asood-rh |
openshift-ci-robot
added
verified-later
verified
|
@asood-rh: This PR has been marked to be verified later by DetailsIn response to this:
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. |
|
/test okd-scos-e2e-aws-ovn |
@oribon What is the new process to bump rpms? |
|
@oribon: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/cherry-pick release-4.20 |
|
@oribon: new pull request created: #111 DetailsIn response to this:
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. |
|
@asood-rh we test it internally on metallb before it gets released |
6 participants
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