Description

Add Sensor health checks to TestPod and TestContainerInstances to prevent test failures caused by insufficient recovery time after Sensor restarts.

Problem

Tests that depend on process event collection (TestPod, TestContainerInstances) can fail when they start immediately after a previous test restarts Sensor. In the analyzed failure:

• TestDelegatedScanning removed LOGLEVEL env variable during cleanup at 15:09:22.540
• This triggered a Sensor pod restart
• TestPod started 0.07 seconds later, before the Collector→Sensor→Central event pipeline fully recovered
• Result: Zero process events collected over 158 seconds, causing test failure

Solution

Added waitForSensorHealthy() function that:

1. Waits for Sensor deployment to be ready in Kubernetes (all replicas running)
2. Waits for Central to report HEALTHY connection status with Sensor
3. Ensures the event collection pipeline is functional before tests proceed

This is called at the beginning of both TestPod and TestContainerInstances, following the same pattern used in TestDelegatedScanning.waitForHealthyCentralSensorConn().

User-facing documentation

• CHANGELOG.md is updated OR update is not needed
• documentation PR is created and is linked above OR is not needed

Testing and quality

• the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
• CI results are inspected

Automated testing

• added unit tests
• added e2e tests
• added regression tests
• added compatibility tests
• modified existing tests

How I validated my change

• Run CI ocp-4-XX-nongroovy-e2e-tests multiple times

Expected CI behavior:

• Tests should wait for Sensor health before starting (new log: "Waiting for Sensor to be healthy before starting test")
• Event collection should succeed after health checks pass
• Tests may take slightly longer due to health check overhead (~2-10 seconds depending on Sensor state)

If tests still fail in CI, the health check timeouts may need adjustment or additional diagnostics may be needed to understand Sensor recovery time.

AI-assisted development

• AI-generated: Initial code structure for waitForSensorHealthy() function and health check calls
• Human-written/verified:
  • Root cause analysis from build logs
  • Import statements and code organization
  • Comments explaining the fix
  • Integration with existing test infrastructure
  • Verification that code compiles and follows existing patterns