Ubuntu 22.04 LTS – cloud-init package stage times out on first boot – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Instance provisioning delays or fails because cloud-init package tasks time out.

Environment & Reproduction

Seen on Jammy cloud images during first boot with slow mirrors or network policy controls.

Root Cause Analysis

cloud-init apt operations race with background updates or unreachable repository endpoints.

Quick Triage

Review cloud-init logs and apt lock ownership to pinpoint timeout stage.

Step-by-Step Diagnosis

Correlate cloud-init module timestamps with apt and network logs.

Solution – Primary Fix

Ensure reachable mirrors and defer overlapping package jobs during cloud-init package stage.

Solution – Alternative Approaches

Pre-bake required packages into images to reduce first-boot dependency on external mirrors.

Verification & Acceptance Criteria

cloud-init reaches done state and all configured package modules complete successfully.

Rollback Plan

Restore prior user-data and cloud-init package configuration if new tuning causes drift.

Prevention & Hardening

Use stable mirrors, deterministic package lists, and controlled first-boot sequencing.

Related Errors & Cross-Refs

Related signals include apt lock contention, temporary DNS failures, and cloud-final timeout warnings.

Related tutorial: View the step-by-step tutorial for Ubuntu 22.04 LTS.

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

cloud-init package module best practices for Ubuntu 22.04 cloud deployments.