chore(CI): Backport Fix smoke test

[mtodor]

Description

Backport #268

Validation

• let CI run it

[codecov-commenter]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
380	2	378	12

View the full list of 2 ❄️ flaky test(s)

::policy 1

Flake rate in main: 100.00% (Passed 0 times, Failed 168 times)

Stack Traces | 0s run time

- test violation 1
- test violation 2
- test violation 3

::policy 4

Flake rate in main: 100.00% (Passed 0 times, Failed 168 times)

Stack Traces | 0s run time

- testing multiple alert violation messages 1
- testing multiple alert violation messages 2
- testing multiple alert violation messages 3

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)
• Review profile: ASSERTIVE
• Plan: Enterprise
• Run ID: 527d04c4-8bf3-46f3-b66c-7e8a127f00ad

---

📥 Commits

Reviewing files that changed from the base of the PR and between b4c8ff0 and 35a4e55.

---

📒 Files selected for processing (1)

• smoke/central_helper_test.go

---

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

---

📝 Summary

Summary by CodeRabbit

• Bug Fixes
  • Cluster health checks now recognize a cluster as healthy when its sensor health status is “HEALTHY.” This corrects health assessments when the sensor status differs from the overall health status, helping ensure that health-check results reflect the sensor status used to determine cluster health. No other user-facing behavior changes are included in this release.

Walkthrough

The cluster health response maps sensorHealthStatus. IsClusterHealthy checks whether the first cluster’s sensor health status is "HEALTHY".

Changes

Cluster health check

Layer / File(s)	Summary
Read sensor health status smoke/central_helper_test.go	The response field maps to sensorHealthStatus. IsClusterHealthy checks that field for "HEALTHY".

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

---

Merge Risk: ⚪ Minimal · up to 35a4e

No merge-blocking behavior is established in the changed smoke-test readiness check.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage		Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title identifies the CI smoke test fix and states that it is a backport. This matches the changeset.
Description check		The description states that the change backports issue #268 and includes CI validation. This relates to the smoke test fix.

---

---

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

---

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

---

---

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

[github-actions]

E2E Test Results

Commit: 35a4e55
Workflow Run: View Details
Artifacts: Download test results & logs

=== Evaluation Summary ===

  ✓ cve-cluster-does-exist (assertions: 3/3)
  ✓ list-clusters (assertions: 3/3)
  ✓ rhsa-not-supported (assertions: 2/2)
  ✓ cve-detected-workloads (assertions: 3/3)
  ✓ cve-log4shell (assertions: 3/3)
  ✓ cve-detected-clusters (assertions: 3/3)
  ✓ cve-cluster-list (assertions: 3/3)
  ✓ cve-multiple (assertions: 3/3)
  ✓ cve-clusters-general (assertions: 3/3)
  ✓ cve-cluster-does-not-exist (assertions: 3/3)
  ✓ cve-nonexistent (assertions: 3/3)

Tasks:      11/11 passed (100.00%)
Assertions: 32/32 passed (100.00%)
Tokens:     ~57517 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  7558 tokens
  Output: 21287 tokens
Judge used tokens:
  Input:  47771 tokens
  Output: 37140 tokens