use build_root from ovnk repo .ci-operator.yaml#74491
Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom Feb 6, 2026
Merged
Conversation
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
Contributor
Author
|
/pj-rehearse |
Contributor
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
|
/pj-rehearse |
Contributor
|
@kyrtapz: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse ack |
Contributor
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
Contributor
Author
|
/pj-rehearse openshift/ovn-kubernetes/release-4.22/unit |
Contributor
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
|
@jluhrsen: job(s): openshift/ovn-kubernetes/release-4.22/unit either don't exist or were not found to be affected, and cannot be rehearsed |
Contributor
Author
|
/pj-rehearse list |
Contributor
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
removed
the
rehearsals-ack
Contributor
|
[REHEARSALNOTIFIER]
A total of 193 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Contributor
Author
|
/pj-rehearse ack |
Contributor
|
@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
Contributor
|
/approve |
openshift-ci
Bot
added
the
approved
Contributor
|
/lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jluhrsen, knobunc 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-merge-bot
Bot
merged commit 371fb59
into
openshift:master
18 of 20 checks passed
Contributor
|
@jluhrsen: 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. |
Sau1506mya
pushed a commit
to Sau1506mya/release
that referenced
this pull request
Feb 9, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
mohit-sheth
pushed a commit
to mohit-sheth/release
that referenced
this pull request
Feb 9, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
theautoroboto
pushed a commit
to theautoroboto/release
that referenced
this pull request
Feb 19, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
dhensel-rh
pushed a commit
to dhensel-rh/release
that referenced
this pull request
Feb 19, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 3, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 3, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
kannon92
pushed a commit
to kannon92/release
that referenced
this pull request
Mar 3, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
kannon92
pushed a commit
to kannon92/release
that referenced
this pull request
Mar 3, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
wangke19
pushed a commit
to wangke19/release
that referenced
this pull request
Mar 4, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
wangke19
pushed a commit
to wangke19/release
that referenced
this pull request
Mar 4, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 5, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 5, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
weinliu
pushed a commit
to weinliu/release
that referenced
this pull request
Mar 6, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
sdodson
pushed a commit
to sdodson/release
that referenced
this pull request
Mar 8, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
sdodson
pushed a commit
to sdodson/release
that referenced
this pull request
Mar 8, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
SeanZhao-redhat
pushed a commit
to SeanZhao-redhat/openshift-release
that referenced
this pull request
Mar 9, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
kasturinarra
pushed a commit
to kasturinarra/release
that referenced
this pull request
Mar 11, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
tareqalayan
pushed a commit
to tareqalayan/release
that referenced
this pull request
Mar 13, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
tareqalayan
pushed a commit
to tareqalayan/release
that referenced
this pull request
Mar 13, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
qiliRedHat
pushed a commit
to qiliRedHat/release
that referenced
this pull request
Mar 13, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
qiliRedHat
pushed a commit
to qiliRedHat/release
that referenced
this pull request
Mar 13, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
MayXuQQ
pushed a commit
to MayXuQQ/release
that referenced
this pull request
Mar 17, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
MayXuQQ
pushed a commit
to MayXuQQ/release
that referenced
this pull request
Mar 17, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
kasturinarra
pushed a commit
to kasturinarra/release
that referenced
this pull request
Mar 17, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
sairameshv
pushed a commit
to sairameshv/release
that referenced
this pull request
Mar 23, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
sairameshv
pushed a commit
to sairameshv/release
that referenced
this pull request
Mar 23, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
zhouying7780
pushed a commit
to zhouying7780/release
that referenced
this pull request
Mar 25, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
zhouying7780
pushed a commit
to zhouying7780/release
that referenced
this pull request
Mar 25, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 25, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
rrasouli
pushed a commit
to rrasouli/release
that referenced
this pull request
Mar 25, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
anpingli
pushed a commit
to anpingli/release
that referenced
this pull request
Mar 30, 2026
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it. Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
anpingli
pushed a commit
to anpingli/release
that referenced
this pull request
Mar 30, 2026
follow up PR to openshift#74491 didn't realize 4.21 would need it as well Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this was probably the intended behavior all along. Using 'from_repository: true' will use what is in the openshift/ovnk .ci-operator.yaml as the build root. That is auto-updated with tooling. Otherwise we have to keep manually bumping it.