[release-4.22] USHIFT-6959 USHIFT-6960 USHIFT-6971 USHIFT-6979 USHIFT-6993 USHIFT-7034: Reorganize optional RF tests#6705
Conversation
Add optional-config.resource with keywords to reconfigure MicroShift's kustomizePaths so each test suite loads only its required manifests.d directories. This avoids running all optional controllers simultaneously, reducing API server contention from concurrent controller wake-ups.
Each optional test suite now reconfigures MicroShift at setup to load only its own manifests.d directory, cleans etcd data, and restarts fresh. Suites that don't need optional components run with base manifests only. Bump TEST_EXECUTION_TIMEOUT to 60m to account for the per-suite restart overhead. Suite-to-manifests.d mapping: - olm.robot: 001-microshift-olm - cert-manager.robot: 060-microshift-cert-manager - gateway-api.robot: 000-microshift-gateway-api - sriov.robot: 070-microshift-sriov - observability.robot: 003-microshift-observability - multus, healthchecks, tls-scanner, GDP: base only
The healthcheck previously determined which optional workloads to wait for by checking whether manifests.d directories exist on the filesystem. This ignored the kustomizePaths configuration, causing the healthcheck to wait for components that were not configured to be deployed. Now the healthcheck also verifies that each optional component path is included in the resolved kustomizePaths before adding it to the wait list. This allows selective loading of optional components via config without the healthcheck timing out on unconfigured ones.
|
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-6959, USHIFT-6960, USHIFT-6971, USHIFT-6979, USHIFT-6993, USHIFT-7034 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. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
pacevedom
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@openshift-cherrypick-robot: This pull request references USHIFT-6959 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.22.0" version, but no target version was set. This pull request references USHIFT-6960 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.22.0" version, but no target version was set. This pull request references USHIFT-6971 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.22.0" version, but no target version was set. This pull request references USHIFT-6979 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.22.0" version, but no target version was set. This pull request references USHIFT-6993 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.22.0" version, but no target version was set. This pull request references USHIFT-7034 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.22.0" version, but no target version was set. 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. |
|
/retest |
|
@openshift-cherrypick-robot: all tests passed! 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. |
|
/verified by CI |
openshift-ci-robot
added
the
verified
|
@pacevedom: This PR has been marked as verified 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, pacevedom 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
|
/label jira/valid-bug |
openshift-ci
Bot
added
jira/valid-bug
openshift-merge-bot
Bot
merged commit 9c4d1c0
into
openshift:release-4.22
3 participants
This is an automated cherry-pick of #6667
/assign pacevedom