Fleet versions

• Discovered: 4.84 / 1.4.0 android
• Reproduced:

Web browser and operating system:

💥  Actual behavior

Unable to resolve host "...": No address associated with hostname

🛠️ To fix

TODO

🧑‍💻  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.

1. Add ~100 certs to your fleet server
2. Enroll a new Android host
3. Monitor logcat for cert statuses
4. Once the first entries begin to appear run gitops against the team where the host is adding the same certs that are already on the team (repeat several time as the enrollment continues)
5. Wait 15 minutes
6. Observe logcat for fleet-ApiClient and fleet-CertificateOrchestrator tags. - adb devices - adb logcat -v time fleet-ApiClient:D fleet-CertificateOrchestrator:D '*:S'
7. The getCertificateTemplate calls fail with Unable to resolve host "...": No address associated with hostname.

🕯️ More info (optional)

N/A

QA

Fixed Android agent to retry DNS resolution failures when waking from Doze mode, and to defer remaining certificates in a batch to the next enrollment cycle when a DNS failure persists.

The fix does not eliminate DNS errors from the logs, it just handles them better.