Closed mmkay closed 9 months ago
Hi @mmkay, thanks for reporting! One thing that might be happening here is that the default timeout for charm-dev
is too small (it is currently 20 minutes). Can you please try adding the parameter --timeout 3600
? This way, it will fail only after one hour.
Hi @luis4a0 - longer timeout seems to do the trick. Based on the logs it looks like it took 21 minutes to start on my setup.
Hi @luis4a0 , is there any way to increase the timeout by default? If the issue is general, then the fix should be general too. (Note: I don't know if me experiencing this issue multiple times and now @mmkay encountering it too counts as general. I'll leave it up to you to decide.)
Hi! Thanks for testing @mmkay! @tmihoc yes, one possibility is to increase the timeout. Slowness usually comes from slow download speeds (not only from Ubuntu repositories: also snaps, PPAs and third-party sites can be slow).
However, examining the charm-dev
definition, I see that many things must be downloaded and installed on the instance. I think thus that increasing a bit the timeout would solve the timeout in some cases. In addition, we should be maybe more verbose in the failure message on Multipass.
Awesome, thanks, @luis4a0 !
@luis4a0 Not sure if related to this, but for the past few days I've also been getting this:
$ multipass shell test-vm
shell failed: ssh failed to authenticate: 'Socket error: disconnected'
If I try again just a moment later, it works. :shrug:
Hey @tmihoc! It may be the same issue. You created the instance, it timed out, but it was finishing the initialization in the background. And It could'nt connect until it finished. That's one possibility, but we can't know exactly what did it happen.
Hi @tmihoc, I believe that is another manifestation of https://github.com/canonical/multipass/issues/3252. We've already fixed it, but we haven't released yet.
Depending on the environment, this can unfortunately happen repeatedly and get annoying. If that is the case, of if you just feel like it, you can get the fix in the "edge" snap channel.
Describe the bug Launching multipass machine based on
charm-dev
blueprint times out. The created machine is however accessible and functional.To Reproduce
Expected behavior Initialization should finish.
Logs
Additional info
multipass version
multipass info --all
Name: charm-dev State: Running IPv4: 10.54.224.17 10.1.157.64 Release: Ubuntu 22.04.3 LTS Image hash: 054db2d88c45 (Ubuntu 22.04 LTS) CPU(s): 4 Load: 0.31 0.15 0.05 Disk usage: 13.1GiB out of 48.4GiB Memory usage: 985.7MiB out of 11.7GiB Mounts: --
Name: charm-dev-vm State: Running IPv4: 10.54.224.95 10.42.163.1 10.1.64.128 Release: Ubuntu 22.04.3 LTS Image hash: 054db2d88c45 (Ubuntu 22.04 LTS) CPU(s): 4 Load: 0.53 0.42 0.43 Disk usage: 9.0GiB out of 29.0GiB Memory usage: 1.7GiB out of 7.7GiB Mounts: --
Name: deb-dev State: Stopped IPv4: -- Release: -- Image hash: 054db2d88c45 (Ubuntu 22.04 LTS) CPU(s): -- Load: -- Disk usage: -- Memory usage: -- Mounts: --
$ multipass get local.driver qemu