Declaration (DDM) profile stuck in "Removing enforcement (pending)"

[noahtalerman]

Fleet version: Observed in Fleet's dogfood (4.66.0)

---

💥  Actual behavior

On my Mac (Host details page here), a DDM profile is stuck:

🧑‍💻  Steps to reproduce

1. Upload DDM profile via UI
2. Delete the profile
3. Quickly upload the same (or modified) profile via the UI
4. Note the deleted profile gets stuck, but the new one does eventually verify

🛠️ To fix

Product designer: @marko-lisica

Deleted profile shouldn't stuck if new one is added.

[noahtalerman]

@georgekarrv @PezHub heads up that we ran into this bug dogfooding. Not sure how we got in this state so I put the bug in the "Inbox" state: https://fleetdm.com/handbook/company/product-groups#inbox

[PezHub]

Hey @noahtalerman I was able to reproduce by:

Method A

1. upload the ddm profile via GitOps
2. modify the same profile and prep it for upload, but wait...
3. delete the profile uploaded in step 1 from the Fleet UI
4. upload the modified profile from step 2 via GitOps soon after deleting the profile in step 3
5. observe you now have two profiles stuck

Method B

1. upload ddm profile via UI
2. delete the profile
3. quickly upload the same (or modified) profle via the UI
4. Note the deleted profile gets stuck but the new one does eventually verify

Method A sounds like a case of needing to follow best practices of using one or the other (GitOps or UI) but Method B does expose a potential bug with ddm profile removals.

[marko-lisica]

Thanks @PezHub, I agree second workflow is a bug. Now when we have GitOps mode, users that use GitOps should use that as best practice, so I wouldn't focus on Method A.

Just to double-check, what are the profile names? I think Fleet should validate that the profile name is unique (file name).