Skip to content

Conversation

yuumasato
Copy link
Contributor

4.15.48 is no longer supported as a version we can deploy in CI.

Keep 4.15 CI job on 4.15 version, not sure if X.Y version works.
Move all other tests to ROSA 4.19.

4.15.48 is no longer supported as a version we can deploy in CI.
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 5, 2025

@yuumasato: This pull request references CMP-3726 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

4.15.48 is no longer supported as a version we can deploy in CI.

Keep 4.15 CI job on 4.15 version, not sure if X.Y version works.
Move all other tests to ROSA 4.19.

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 Sep 5, 2025
@yuumasato yuumasato changed the title CMP-3726: Update ROSA version used for CI CMP-3726: Update ROSA version used for compliance-operator CI Sep 5, 2025
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@yuumasato: 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
pull-ci-ComplianceAsCode-compliance-operator-master-e2e-rosa ComplianceAsCode/compliance-operator presubmit Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-1.7-e2e-rosa ComplianceAsCode/compliance-operator presubmit Ci-operator config changed
pull-ci-ComplianceAsCode-compliance-operator-1.6-e2e-rosa ComplianceAsCode/compliance-operator presubmit Ci-operator config changed
pull-ci-ComplianceAsCode-content-master-4.15-e2e-rosa-ocp4-cis-node ComplianceAsCode/content presubmit Ci-operator config changed
pull-ci-ComplianceAsCode-content-master-4.15-e2e-rosa-ocp4-pci-dss-node ComplianceAsCode/content presubmit Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.

@rhmdnd
Copy link
Contributor

rhmdnd commented Sep 5, 2025

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

Copy link
Contributor

@rhmdnd rhmdnd left a comment

Choose a reason for hiding this comment

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

/lgtm

Let's see what CI says, but thanks for updating these.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 5, 2025
Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd, yuumasato

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@yuumasato
Copy link
Contributor Author

@rhmdnd So 4.15 is really not available.
Is there a reason we only had the e2e-rosa test only on 4.15?

@rhmdnd
Copy link
Contributor

rhmdnd commented Sep 5, 2025

@rhmdnd So 4.15 is really not available. Is there a reason we only had the e2e-rosa test only on 4.15?

I think that's just what was available at the time we stood up this CI. We can bump the version forward if needed. At the time, there wasn't a latest option (at least not that I recall).

Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

@yuumasato: 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/rehearse/ComplianceAsCode/content/master/4.15-e2e-rosa-ocp4-pci-dss-node 8c9455c link unknown /pj-rehearse pull-ci-ComplianceAsCode-content-master-4.15-e2e-rosa-ocp4-pci-dss-node
ci/rehearse/ComplianceAsCode/content/master/4.15-e2e-rosa-ocp4-cis-node 8c9455c link unknown /pj-rehearse pull-ci-ComplianceAsCode-content-master-4.15-e2e-rosa-ocp4-cis-node
ci/rehearse/ComplianceAsCode/compliance-operator/1.7/e2e-rosa 8c9455c link unknown /pj-rehearse pull-ci-ComplianceAsCode-compliance-operator-1.7-e2e-rosa

Full PR test history. Your PR dashboard.

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
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants