22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-images |
Triaged
|
High
|
Unassigned | ||
| livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Jammy |
Confirmed
|
Undecided
|
Unassigned | ||
| Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
[ SRU TEMPLATE ]
[Impact]
* 22.04 and 22.10 images will fail to boot on older versions of vagrant due to ssh key issues. this prevents users of 18.04 and 20.04 vagrant from the archives to use 22.04 images
* Not making this change, 22.04 vagrant images will continue to be unbootble on vagrant < 2.2.16.
[Test Plan]
* reproduce by
1. having vagrant < 2.2.16 installed on your system (such as having a 20.04 host and doing apt-get install vagrant)
2. vagrant init ubuntu/jammy64
3. vagrant up
4. observe the failure to connect
* to test
1. ensure vagrant < 2.2.16 is installed
2. download a provided test box
3. vagrant box add <path/to/test/box> --name test-jammy64
4. vagrant init test-jammy64
5. vagrant up
6. observe image booting properly
[Where problems could occur]
* It is possible that the new key is of a type not recognized on old enough systems (it uses ed25519 which has been supported for a while, but may not be supported on all systems). having wide community testing with many different hosts and versions of vagrant will be helpful
[ Original Bug ]
currently published 22.04 Vagrant images will fail to finish booting on systems running vagrant < 2.2.16. The upstream issue is described here:
https:/
The fix in future vagrant versions is committed here:
https:/
However, vagrant, as supplied as a package in the Ubuntu archive in Universe is not => 2.2.16 until Jammy. This means that host systems of 20.04, 18.04, and 16.04 using the universe packaged vagrant will be unable to start the Jammy image.
A workaround is stated in gh issue 11783: to provide our own newer key that matches the algorithms that the guest system expects, without needing the renegotiation fix put in place in vagrant.
| Changed in cloud-images: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| John Chittum (jchittum) wrote | #1 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in livecd-rootfs (Ubuntu): | |
| status: | New → Confirmed |
| Olaf Mandel (olafmandel) wrote | #3 |
| Erik Sommer (erik-sommer) wrote | #4 |
| summary: |
- 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout + 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in livecd-rootfs (Ubuntu Kinetic): | |
| status: | Confirmed → Fix Released |
| John Chittum (jchittum) wrote | #6 |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in livecd-rootfs (Ubuntu Jammy): | |
| status: | New → Confirmed |
a test image has been made and available at
https:/
This image uses an ed25519 key created at build time, included in the `.box`, and referenced in the default image Vagrantfile. This image is meant to work on a wider number of vagrant versions, as supplied in Ubuntu universe
I tested this on Focal with Virtualbox 6.1 and vagrant 2.2.6, and it was able to complete the bootstrap SSH step.