-
Notifications
You must be signed in to change notification settings - Fork 474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profile removal fails if host never received the profile #21891
Comments
…led (#22186) > Related issue: #21891 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Added/updated tests - [x] Manual QA for all new/changed functionality
Hey @jahzielv I'm still seeing this issue and can reproduce by uploading a profile to a team then quickly deleting it before it gets installed on the host. Fleet sends the remove command to the host without the profile installed so the uninstall fails. Here's a loom video walk thru (including a workaround to fix at the end) I believe it may be related to this issue as well #22121 |
Ok, I think I've figured out why that's happening. We're currently removing profiles that never made it to the host in a cron job, but adding and quickly deleting will most likely happen in between cron job runs, so the logic that removes the profile doesn't happen and the zombie host profile hangs around. Now I have to figure out a way to catch profiles in that state without the cron job; I'll report back when I have something. |
> Follow up on: #21891 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] Added/updated tests - [x] Manual QA for all new/changed functionality
Profile removal glitch, |
We are still seeing this after upgrading to 4.58. |
|
@jahzielv @georgekarrv Heads up this was re-opened. Please take a look and try to get a fix into v4.60.0 if possible. Thanks! |
@jahzielv @georgekarrv I see v4.60.0 won't work since we're in deep freeze, but I'm adding P2 so we can prioritize over other bugs next week. |
Re-closing this bug; a feature request for product consideration has been filed here: #24264 |
Profile removal fail, |
Fleet version: 4.55.0 and in Dogfood SNAPSHOT-1874915
💥 Actual behavior
When a macOS configuration profile is added to a team and then removed from that team before a host comes online, Fleet will send an MDM command to remove the profile from that host. However, since the profile was never delivered, the removal command fails:
🧑💻 Steps to reproduce
Failed
under OS settings. You’ll see that Fleet attempted to send a RemoveProfile MDM command that failed because the profile with that identifier never existed on the host.🕯️ More info (optional)
The text was updated successfully, but these errors were encountered: