Skip to content

VPP Token Assignment and GitOps Issue #32432

@reeblybeebly

Description

@reeblybeebly

Fleet version: 4.72.0


💥  Actual behavior

customer-kokkola stated that when attempting to configure VPP assignment via gitops they receive an error for an existing team, there is however no error when performing a dry-run of the same gitops update.

Error Message

[+] applying 4 app store apps for team <customer> VIP Computers
Error: applying app store apps for team: "<customer> VIP Computers": POST /api/latest/fleet/software/app_store_apps/batch received status 422 Unprocessable Entity: could not retrieve vpp token: No available VPP Token

🛠️ To fix

Product designer: @marko-lisica

If running the command without the dry-run flag throws an error, the same error should occur when running with the dry-run flag.

When a team doesn't have a VPP token assigned, we see the expected error in GitOps when adding app_store_apps to a team YAML file. We should see the same error when running command with --dry-run flag.

🧑‍💻  Steps to reproduce

  1. Confirmed with customer errors did not appear in dry-run
  2. Confirmed with customer that this team did already exist prior to performing gitops update

🕯️ More info (optional)

Slack Threads
https://fleetdm.slack.com/archives/C08HNQD4XP1/p1756381134939989
https://fleetdm.slack.com/archives/C019WG4GH0A/p1756313045609699

Metadata

Metadata

Assignees

Labels

#g-mdmMDM product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedcustomer-eponymcustomer-kokkola

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions