Repository navigation
Open
Labels
#g-apple-at-workProduct group focused on Apple devicesProduct group focused on Apple devicesP2Urgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needUrgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needbugSomething isn't working as documentedSomething isn't working as documentedcustomer-antonella
Description
Fleet versions
- Discovered: 4.94.1
- Reproduced: Not yet reproduced outside the customer's environment
Web browser and operating system: N/A (server-side, during ADE Setup Assistant). Affected hosts run macOS 27.0, 27.2 and 27.2.1. Seen on Mac17,6, 17,7, 17,12 and 17,13.
💥 Actual behavior
On macOS 27, ADE Macs in a Fleet with macos_updates.update_new_hosts: true and no minimum_version aren't required to update during Setup Assistant. Fleet logs getting apple software update required err="no matching asset found for device Mac17,x" and continues to end-user authentication.
🛠️ Expected behavior
When GDMF offers a newer macOS version for the Mac's board ID, Fleet requires the update during Setup Assistant, as it does for Macs on macOS 26.x.
🧑💻 Steps to reproduce
These steps:
- Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
- Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.
- On Fleet 4.94.1, set
macos_updates.update_new_hosts: truewith nominimum_versionon a Fleet with end-user authentication enabled. - Assign an ADE Mac running macOS 27.x to that Fleet and start Setup Assistant.
- Check the server logs for
no matching asset found for device ..., and confirm the Mac isn't asked to update.
🕯️ More info (optional)
- Same Mac, different OS: a Mac17,7 was checked with no error on macOS 26.5.1. The same Mac errored after it was on 27.2.1.
- Correct board IDs are stored and cached: the affected hosts'
host_mdm_apple_os_updates.software_update_device_idhold valid board IDs (K116sAP,J714cAP), and both are in the cached GDMF assets. The GDMF cache refreshed after the 27.2.1 posting, and a manualapple_mdm_os_updatestrigger didn't help. - Suspected cause:
gdmf.GetLatestOSVersionmatches onPRODUCTorSOFTWARE_UPDATE_DEVICE_IDfrom MachineInfo. If macOS 27 leaves outSOFTWARE_UPDATE_DEVICE_IDin the Setup Assistant MachineInfo, Fleet comparesMac17,xagainst board IDs and never matches. The correct stored value may come later from osquery. - Logging gap: the error only prints
PRODUCT. It would help to also logSOFTWARE_UPDATE_DEVICE_ID. - Related: update_new_hosts fails silently when the GDMF asset cache has no row for the device model #53262 (empty cache, same error, different cause).
- Internal Pylon Issue #2877
Metadata
Metadata
Assignees
Labels
#g-apple-at-workProduct group focused on Apple devicesProduct group focused on Apple devicesP2Urgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needUrgent: Supported workflow not functioning as intended, newly drafted feature with urgent Fleet needbugSomething isn't working as documentedSomething isn't working as documentedcustomer-antonella
Type
Projects
- StatusShow more project fields📨 Inbox
- StatusShow more project fields📨 Inbox
Activity
MrNRod commentedon Nov 13, 2026
@georgekarrv requesting P2 for this one.
Why:
update_new_hostsis a supported workflow, and on macOS 27 it isn't functioning as intended. ADE Macs on 27.x go through Setup Assistant without being required to update, even when GDMF offers a newer version.Customer impact (customer-antonella): They rely on
update_new_hoststo make sure new hires' Macs are current before day one, because Fleet doesn't yet support minimum OS enforcement at enrollment (#40121, #53647). Right now there's no workaround on our side, so Macs are reaching end users out of date.Scope is growing: this appears to affect any Mac enrolling on macOS 27, not specific hardware. The same Mac matched with no error on 26.5.1 and failed on 27.2.1, and an M5 on 26.x still updates. As more Macs ship with or upgrade to 27, more enrollments will be affected. The newest MacBook Pro models (Mac17,10–13) can't run macOS 26 at all.
Happy to help reproduce or pull more logs from the customer.
Pylon Issue #2877