USHIFT-6740: skip running tls-scanner on cas10-src-optional arm

[eslutsky]

No description provided.

[openshift-ci-robot]

@eslutsky: This pull request references USHIFT-6740 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.

Details

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 84beafa6-a787-4baf-a193-5e409909f20d

📥 Commits

Reviewing files that changed from the base of the PR and between 6891c03 and 421c109.

📒 Files selected for processing (1)

• test/scenarios-bootc/upstream/cos10-src@optional.sh

---

Walkthrough

scenario_run_tests() now builds a skip_args string initialized with --skip sriov and appends --skip tls-scanner when UNAME_M is aarch64. The run_tests host1 invocation is updated to use ${skip_args} instead of a fixed --skip sriov argument.

Changes

Cohort / File(s)	Summary
Skip arguments refactor test/scenarios-bootc/upstream/cos10-src@optional.sh	Replaced hardcoded --skip sriov with a dynamically constructed skip_args variable (always includes --skip sriov, appends --skip tls-scanner on aarch64) and updated run_tests host1 to use ${skip_args} (with shellcheck suppression for word-splitting).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [eslutsky]

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@test/scenarios-bootc/upstream/cos10-src`@optional.sh:
- Around line 27-31: The test invocation is incorrectly quoting "${skip_args}"
which makes the whole skip string a single argument; update the run_tests call
(the line invoking run_tests with PROMETHEUS_HOST and LOKI_HOST) to use an
unquoted ${skip_args} so the --skip option and its value are passed as separate
argv entries (follow the pattern used in el98-lrel@optional.sh and add the
shellcheck disable comment if needed to suppress SC2086).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 6ec7fd8b-c4ea-4cbf-a4e7-5139053ae34a

📥 Commits

Reviewing files that changed from the base of the PR and between 5e95c78 and 6891c03.

📒 Files selected for processing (1)

• test/scenarios-bootc/upstream/cos10-src@optional.sh

[eslutsky]

/retest

[openshift-ci]

@eslutsky: 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/prow/e2e-aws-tests-bootc-upstream-arm	6891c03	link	true	/test e2e-aws-tests-bootc-upstream-arm
ci/prow/e2e-aws-tests-bootc-upstream	6891c03	link	true	/test e2e-aws-tests-bootc-upstream

Full PR test history. Your PR dashboard.

Details

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.