Open PezHub opened 1 week ago
QA Notes:
Confirmed I was able to enroll my device via ADE after the fix was applied. It does sit on the Remote management page for a few minutes but that is due to -
a "worker job" that runs, checks if every required MDM command and profile have been delivered, if not it retries after a bit, checks again, retries, etc. And the delays between retries are always increasing (I think it's 1m, 5m, 10m) before eventually giving up and releasing the device even if not all profiles have been delivered. Depending on what attempt succeeds, it can take a while but should always be at most 15-16mins.
Fleet version: 4.59 unreleased
main
Web browser and operating system: N/A
💥 Actual behavior
The new workflow introduced for setup experience leverages the latest version of fleetd when automatically enrolling macs via ABM. This means customers hosting their own fleet and tuf servers (with older versions of fleetd) will not be able to enroll their mac devices via ABM. Currently the host will get stuck in the
"Waiting for management server..."
Remote management page🧑💻 Steps to reproduce
🕯️ More info (optional)
N/A