USHIFT-3138: Refactor scenarios not to exceed 20m runtime in pre-submits

[ggiguash]

• Splitting the osconfig tests to 3 scenarios in bootc only
• Moving certificate rotation test from standard1 to standard2 to balance them out

Note: when we create periodic tests for bootc, we will likely merge the osconfig tests back into one scenario, similar to what we have in composer-cli periodics.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ggiguash]

/test ?

[openshift-ci]

@ggiguash: The following commands are available to trigger required jobs:

• /test images
• /test metal-bootc-test
• /test metal-bootc-test-arm
• /test metal-periodic-test
• /test metal-periodic-test-arm
• /test microshift-metal-cache
• /test microshift-metal-cache-arm
• /test microshift-metal-tests
• /test microshift-metal-tests-arm
• /test ocp-conformance-rhel-eus
• /test ocp-conformance-rhel-eus-arm
• /test test-rpm
• /test test-unit
• /test verify

The following commands are available to trigger optional jobs:

• /test test-rebase

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-microshift-main-images
• pull-ci-openshift-microshift-main-metal-bootc-test
• pull-ci-openshift-microshift-main-metal-bootc-test-arm
• pull-ci-openshift-microshift-main-microshift-metal-tests
• pull-ci-openshift-microshift-main-microshift-metal-tests-arm
• pull-ci-openshift-microshift-main-test-unit
• pull-ci-openshift-microshift-main-verify

In response to this:

/test ?

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/test-infra repository.

[ggiguash]

/test metal-bootc-test
/test metal-bootc-test-arm

[ggiguash]

/test metal-bootc-test
/test metal-bootc-test-arm

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In 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.

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

• Splitting the osconfig tests to 3 scenarios in bootc only
• Moving certificate rotation test to standard 2 to balance them out

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]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

• Splitting the osconfig tests to 3 scenarios in bootc only
• Moving certificate rotation test from standard1 to standard2 to balance them out

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]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

• Splitting the osconfig tests to 3 scenarios in bootc only
• Reduce the amount of restart attempts in the lifecycle test to reduce the overall runtime without hurting the testability
• Moving certificate rotation test from standard1 to standard2 to balance them out

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]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

• Splitting the osconfig tests to 3 scenarios in bootc only
• Reduce the amount of restart attempts in the lifecycle test to reduce the overall runtime without hurting the testability
• Moving certificate rotation test from standard1 to standard2 to balance them out

Note: when we run periodic tests for bootc, we will likely merge the osconfig tests back into one scenario, similar to what we have in composer-cli periodics.

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]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

• Splitting the osconfig tests to 3 scenarios in bootc only
• Reduce the amount of restart attempts in the lifecycle test to reduce the overall runtime without hurting the testability
• Moving certificate rotation test from standard1 to standard2 to balance them out

Note: when we create periodic tests for bootc, we will likely merge the osconfig tests back into one scenario, similar to what we have in composer-cli periodics.

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.

[ggiguash]

/assign @pmtk

[copejon]

Can we rename the scenario scripts to something more descriptive? Using osconfig1..5 doesn't indicate much outside of a general context for the scenario under test.

[ggiguash]

/test metal-bootc-test-arm

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-3138 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

• Splitting the osconfig tests to 3 scenarios in bootc only
• Moving certificate rotation test from standard1 to standard2 to balance them out

Note: when we create periodic tests for bootc, we will likely merge the osconfig tests back into one scenario, similar to what we have in composer-cli periodics.

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.

[pmtk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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:

• OWNERS [ggiguash,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@ggiguash: all tests passed!

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.