Network check runs forever
Metadata
Current evaluation
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.
Resolution: closed resolved
Reason: Snapcraft 7.5.4 changed the failed network check from infinite retries to a timeout, resolving the hang described in #4412; #4443 records the same LXD symptom. craft-providers #185 documents network troubleshooting, while #189 adds an internet check after a network command failure.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
If the `getent` call to check for networking fails, it retries (which is good), but it retries forever, leading to an eternal spin. We need a documentation link for the error to help troubleshoot too.
### To Reproduce
Do the reverse of
```
sudo ufw allow in on lxdbr0
sudo ufw route allow in on lxdbr0
sudo ufw route allow out on lxdbr0
```
and run snapcraft pack on a new project.
### Environment
Ubuntu
### snapcraft.yaml
```shell
n/a
```
### Relevant log output
```shell
n/a
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | 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. | |
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft 7.5.4 added a timeout for the failed LXD network check, ending the indefinite retry loop; #4443 documented the related ARM64 case. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Snapcraft 7.5.4: the LXD getent network wait now times out instead of retrying forever. Snapcraft#4443 confirms the timeout resolves the same missing-network hang. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved in Snapcraft 7.5.4 by replacing the endless LXD network wait with a timeout; friendly networking troubleshooting errors were added earlier in PR #1930. | |
| stealth/space-bunny-alpha | — | closed resolved | The endless LXD network wait was fixed by a timeout in Snapcraft 7.5.4, as reported in #4443. Earlier LXD handling also gained friendly troubleshooting errors in #1930. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Maintainer confirmed craft-providers 7.x and 8.x resolve the infinite network retry loop, with tests added to verify the fix across versions. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed pending verification of upstream fixes in craft-providers 7.x and 8.x. Resolution relies on external patches, with plans to add regression tests for the infinite network check retry loop. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The infinite network retry loop was resolved via a craft-providers fix for versions 7.x and 8.x. Maintainer will verify the fix across both versions and add regression tests. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as fixed in craft-providers 7.x and 8.x. The infinite network check retry loop was resolved in newer releases. Maintainers verified the fix and requested test coverage for affected scenarios. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/snapcraft#4443
(confidence 95%)
Related Snapcraft report of the LXD network hang; the timeout fix is associated with Snapcraft 7.5.4.
-
Related To:
canonical/craft-providers#185
(confidence 90%)
Adds an explanation and troubleshooting guidance for network issues.
-
Related To:
canonical/craft-providers#189
(confidence 85%)
Adds an internet check after a network command fails, covering failed network-check handling.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4443 snapcraft on ARM 64 - stuck at lxd | snapcraft | closed | The ARM64 hang was traced to missing LXD container networking, not a Snapcraft architecture defect; Snapcraft 7.5.4 added a timeout instead of looping indefinitely. | |
| #1999321 Snapcraft is stuck on "launching instance..." indefinitely | snapcraft (launchpad) | open | Endless LXD startup on failed container DNS now times out via craft-providers; Snapcraft 7.5.4 is recorded as fixing the wait. Multipass arm64 and Docker diagnostics remain separately tracked. | |
| #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. | |
| #2093417 craft-providers error: Timed out waiting for networking to be ready. | snapcraft (launchpad) | open | 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. |