Skip to content

e2e: fix vlagent path collision in upgrade tests#2305

Open
AndrewChubatiuk wants to merge 1 commit into
masterfrom
fix-vlagent-upgrade-test-collision
Open

e2e: fix vlagent path collision in upgrade tests#2305
AndrewChubatiuk wants to merge 1 commit into
masterfrom
fix-vlagent-upgrade-test-collision

Conversation

@AndrewChubatiuk

@AndrewChubatiuk AndrewChubatiuk commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

upgrade tests may run multiple collectors in parallel, that mount same host path, which lead to vlagent crashes


Summary by cubic

Fixes VLAgent upgrade e2e test crashes caused by HostPath collisions when multiple collectors run in parallel. Each test now uses a version-scoped tmp data path and volume to prevent mount conflicts.

  • Bug Fixes
    • Added vlagentK8sCollector to enable the k8s collector and set a unique TmpDataPath and HostPath per version (e.g., /var/lib/vlagent-data-<version>), with matching Volume/VolumeMount (tmp-data).
    • Introduced withVersion and updated crVersionPair.cr to a factory func(string) client.Object, so objects are created with the test’s version and unique paths.
    • Replaced repeated inline vlagent k8s collector configs with vlagentK8sCollector across versions v0.68.0v0.71.0.

Written for commit 230cfe4. Summary will update on new commits.

Review in cubic

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants