stackrox(perfscale): pin ocp version#73276
stackrox(perfscale): pin ocp version#73276openshift-merge-bot[bot] merged 5 commits intoopenshift:masterfrom
Conversation
openshift-ci
Bot
added
do-not-merge/hold
|
/pj-rehearse |
|
@davdhacs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@davdhacs: 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
|
/unhold |
openshift-ci
Bot
removed
the
do-not-merge/hold
| version: "4.19" | ||
| release: | ||
| channel: stable | ||
| version: "4.20" |
There was a problem hiding this comment.
tbh. I would pin it to strict patch. If we use stable channel we could still get instability from 4.20.z updates. @davdhacs What do you think?
There was a problem hiding this comment.
good idea. How about 4.20.8 (Dec 12, then 4.20.9 was released Jan 9)?
|
/pj-rehearse periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test |
|
@davdhacs: 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
|
/pj-rehearse periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test |
|
@davdhacs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test |
|
@davdhacs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
Log Snippet INFO[2026-01-19T16:39:57Z] Requesting latest release from https://api.integration.openshift.com/api/upgrades_info/graph?arch=amd64&channel=stable-4.20 Build Log URL |
|
/pj-rehearse ack |
|
@davdhacs: 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
|
I think I should wait until stable-4.20 reaches a new version and then we can verify this still gets a 4.20.8 ocp instead of later. |
|
/pj-rehearse periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test |
|
@davdhacs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
It was updated to 4.20.10 Jan 21: So this verifies the pinning works. |
|
/pj-rehearse periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test I'm re-running it as an extra sanity check. I don't think the stream would get the wrong version more than 12 hours after the update, but I'd like to be certain it still get the 4.20.8 version now, days later. |
|
@davdhacs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@davdhacs: 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. |
|
Confirmed it stayed on 4.20.8 for the re-run yesterday (https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/73276/rehearse-73276-periodic-ci-stackrox-stackrox-nightlies-perf-scale-24nodes-scale-scannerv4-test/2015833599240048640): |
|
/pj-rehearse ack |
|
@davdhacs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davdhacs, mtodor 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 f004842
into
openshift:master
* stackrox(perfscale): pin ocp version * pin perfscale to 4.20.8 * unquoted
* stackrox(perfscale): pin ocp version * pin perfscale to 4.20.8 * unquoted
* stackrox(perfscale): pin ocp version * pin perfscale to 4.20.8 * unquoted
* stackrox(perfscale): pin ocp version * pin perfscale to 4.20.8 * unquoted
* stackrox(perfscale): pin ocp version * pin perfscale to 4.20.8 * unquoted
* stackrox(perfscale): pin ocp version * pin perfscale to 4.20.8 * unquoted
3 participants
We want to test with an un-changing OCP version so that differences in metrics are because of stackrox changes and not openshift changes.
https://docs.ci.openshift.org/docs/architecture/ci-operator/#testing-with-an-existing-openshift-release