[Bug 1969664] Re: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout

[John Chittum]

Kinetic Vagrant image is available at :
https://app.vagrantup.com/ubuntu/boxes/kinetic64

for a fresh install quickly

vagrant init ubuntu/kinetic64
vagrant up

This image should work on all versions of Vagrant available in Ubuntu
archives.  I'll spin some VMs and do more testing, but community help is
appreciated. Once a few versions of Vagrant and hosts are verified,
we'll be able to do an SRU to Jammy

Testing
******************

Host: Ubuntu 22.04
Vagrant: 2.2.19
Virtualbox: 6.1
VBox Guest Additions: 6.0.0 r127566

successful boot and ssh. no errors

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1969664

Title:
  22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout

Status in cloud-images:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  New
Status in livecd-rootfs source package in Kinetic:
  Fix Released

Bug description:
  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://github.com/hashicorp/vagrant/issues/11783

  The fix in future vagrant versions is committed here:

  https://github.com/hashicorp/vagrant/pull/12298

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1969664/+subscriptions