craft-providers error: Timed out waiting for networking to be ready.
Metadata
Current evaluation
Snapcraft 8.5.1 with --use-lxd fails with 'craft-providers error: Timed out waiting for networking to be ready' during the getent hosts readiness check. Same report filed upstream as craft-providers#714; untriaged here, no maintainer response.
Suggested action: needs triage
Reason: The issue has no labels, no assignee and the only comment is the author's empty submission 630 days ago, so it shows no sign of maintainer triage; the failing check lives in craft-providers, not snapcraft (the log line comes from the provider's instance start-up networking probe), which is why the author also opened canonical/craft-providers#714. It is a build-blocking error with a trace excerpt but the root cause is host-specific LXD/DNS behaviour and the report includes no host/network diagnostics, so a maintainer needs to decide whether to keep it here or defer to the upstream issue.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
6
Complexity:
65
Confidence:
70
Actionability:
45
|
needs triage | Snapcraft 8.5.1 with --use-lxd fails with 'craft-providers error: Timed out waiting for networking to be ready' during the getent hosts readiness check. Same report filed upstream as craft-providers#714; untriaged here, no maintainer response. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
7
Complexity:
62
Confidence:
72
Actionability:
38
|
needs triage | Snapcraft 8.5.1 --use-lxd build aborts with craft-providers 'Timed out waiting for networking to be ready' during base instance setup; duplicate of craft-providers#714, untriaged here with no host/network diagnostics. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
4
Complexity:
70
Confidence:
72
Actionability:
28
|
needs triage | Snapcraft 8.5.1 with --use-lxd fails with 'craft-providers error: Timed out waiting for networking to be ready.' from the provider's getent/DNS readiness check. Duplicate report for craft-providers#714; untriaged here, no diagnostics provided. | |
| stealth/space-bunny-alpha |
Impact:
54
Quick Win:
10
Complexity:
58
Confidence:
83
Actionability:
45
|
needs triage | Snapcraft 8.5.1 with LXD times out checking container networking during a build. Untriaged, with no comments; the identical craft-providers report remains open. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
30
Staleness:
95
Complexity:
40
Confidence:
70
Support Request:
30
|
close stale | craft-providers times out waiting for networking in LXD container during snap builds. Open 602 days with no maintainer response, labels, or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
40
Confidence:
75
Support Request:
20
|
needs triage | Reports a craft-providers networking timeout error during snapcraft builds. Unlabelled, no maintainer response, and inactive for over 1.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
75
|
close stale | Report of craft-providers networking timeout during LXD-based snap builds. Issue is 558 days old with no maintainer response or comments, currently inactive and untriaged. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | External contributor reports a craft-providers networking timeout when building with LXD. Issue is 545 days old with no maintainer comments or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
canonical/craft-providers#714
(confidence 95%)
Explicitly linked in the body ('Reported against Craft-Providers too') and that upstream issue is still open with the same title and log.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #714 craft-providers error: Timed out waiting for networking to be ready. | craft-providers | open | Open Type: Bug report: Snapcraft 8.5.1 LXD builds time out while getent checks DNS for snapcraft.io; host/network context and a part YAML are missing, leaving the root cause unknown. | |
| #1047 Charmcraft stuck on "launching environment" | charmcraft | closed | Craft-providers now verifies network connectivity and times out hung LXD setup, preventing indefinite waits; underlying LXD/Docker firewall conflicts may still require configuration. | |
| #4412 Network check runs forever | snapcraft | closed | Infinite getent/LXD network retries were fixed by a timeout shipped in Snapcraft 7.5.4; #4443 documents the related ARM64 hang and craft-providers added troubleshooting. |