canonical / canonical/multipass

Be more verbose in timeout failures

Open
#3,314 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
C++
Stars
9.2k
Forks
828
Avg merge
3d 1h
Merged PRs (30d)
44

Description

**What are you trying to do?**
When a user tries to launch an instance and it timeouts, the failure message does not give more information. This can be misleading, because the instance in some cases is indeed created and available to the user.

**What's your proposed solution?**
The failure message is currently "timed out waiting for initialization to complete". We should add something like "try to use the --timeout parameter to increase the waiting time", or suggest that the instance might have been created.

**Additional context**
https://github.com/canonical/multipass/issues/3310

Contributor guide

Open the contributing guide

Research direction

Start by tracing the CLI path that launches an instance and reports "timed out waiting for initialization to complete". Review related issue #3310 and inspect how the --timeout parameter is handled. Done means timeout failures explain that the instance may still have been created and advise how increasing --timeout may help, with the relevant behavior covered by tests if this path has existing coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.