fix(e2e): run snapshot from CI runner instead of nested Job#199
Closed
fix(e2e): run snapshot from CI runner instead of nested Job#199
Conversation
The snapshot command always deploys an agent Job — running it inside a manually-created Job caused a nested deploy attempt that failed with UNAUTHORIZED (the pod ServiceAccount lacked RBAC to create Jobs). Run `aicr snapshot` from the CI runner instead, letting the command handle its own Job deployment to the Kind cluster.
lockwobr
approved these changes
Feb 24, 2026
dims
approved these changes
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
kubectl applyJob with directaicr snapshotinvocation from the CI runnerRoot cause
The
--deploy-agentflag was removed —aicr snapshotnow always deploys an agent Job. The E2E test was creating a manual Job that ranaicr snapshotinside the cluster, which caused a nested agent deployment attempt. The pod's ServiceAccount lacked RBAC to create Jobs/Roles/ServiceAccounts, failing withUNAUTHORIZED.Fix
Run
aicr snapshotfrom the CI runner (outside the cluster) and let it handle its own Job deployment, RBAC, and cleanup. This matches how the command is actually used.Test plan
bash -n tests/e2e/run.sh— syntax valid