Managed FetchService should not start the fetch-service
Metadata
Current evaluation
Managed FetchService no longer starts fetch-service; fixed by merged PR #542 at commit 6efe5447.
Resolution: closed resolved
Reason: PR #542 changed managed mode so FetchService does not attempt to start the service inside the build instance. The PR was merged as commit 6efe5447 and explicitly resolved #537.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
The managed version of the FetchService, which is used when packing to create the project manifest, should not try to start the fetch-service from inside the instance. It's actually surprising that it doesn't fail every time, only sometimes.
### To Reproduce
Run `pack` with `--enable-fetch-service=permissive`
### part yaml
```shell
.
```
### Relevant log output
```shell
❯ rockcraft pack --enable-fetch-service=permissive
Warning: the fetch-service integration is experimental and still in development.rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
Warning: the fetch-service integration is experimental and still in development.
The 'fetch-service' snap is not installed.
Recommended resolution: Install the fetch-service snap via 'snap install --channel=beta fetch-service'.
Failed to execute rockcraft in instance.
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Managed FetchService no longer starts fetch-service; fixed by merged PR #542 at commit 6efe5447. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a recorded fix or explanation; the sole comment was an automated notice creating internal ticket CRAFT-3601. | |
| stealth/space-bunny-alpha | — | closed stale | Closed with no documented fix or superseding change after about two years of inactivity; an automated comment recorded internal ticket CRAFT-3601. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a public resolution. Synced to internal Jira ticket CRAFT-3601. No fix or merge details were documented, suggesting the issue was abandoned or resolved internally. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix or resolution documented. The managed FetchService incorrectly attempted to start the fetch-service during pack, causing failures. No code changes or merge details were provided. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#542
(confidence 100%)
Merged fix preventing fetch-service startup in managed mode; merged as commit 6efe5447.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #542 fix: don't start the fetch-service in managed mode | craft-application | merged | Merged PR #542 as commit 6efe5447, preventing fetch-service startup in managed mode and resolving #537. |