Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update machine1 from Ubuntu 22.04 to 24.04 #196

Closed
wants to merge 0 commits into from

Conversation

ttwd80
Copy link
Contributor

@ttwd80 ttwd80 commented Sep 5, 2024

Description

The result of the workflow will be a Ubuntu 24.04 host. Previously this was a 22.04 host.

Why is this needed

Ubuntu 24.04 is the latest LTS release.

Fixes: #

How Has This Been Tested?

  • Tested with libvirt as the vagrant provider on Ubuntu 22.04.1 (x64).
  • Tested with virtualbox as the vagrant provider on Ubuntu 22.04.1 (x64).

How are existing users impacted? What migration steps/scripts do we need?

  • Ubuntu 24.04 has a /boot partition, Ubuntu 22.04 had /boot on the / partition. The kexec portion has been updated to mount the /boot partition. No change is required to run the steps. The change was introduced in the workflow template.

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

@ttwd80 ttwd80 changed the title Update ouput from Ubuntu 22.04 to 24.04 Update machine1 from Ubuntu 22.04 to 24.04 Sep 5, 2024
@ttwd80 ttwd80 marked this pull request as ready for review September 5, 2024 19:12
@jacobweinstock
Copy link
Member

Hey @ttwd80 . Thanks for this. Mind squashing all these commits with duplicate comments? Update VAGRANTVBOX.md and Update VAGRANTLVIRT.md

@@ -76,7 +76,7 @@ Vagrant.configure("2") do |config|
v.memory = 2048
v.cpus = 2
v.gui = true
v.customize ["modifyvm", :id, "--nic1", "hostonlynet", "--nic2", "nat", "--boot1", "disk", "--boot2", "net"]
Copy link
Member

@jacobweinstock jacobweinstock Sep 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me, this change causes the VM not to start and give the error:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "49c31a7a-eb66-46cb-a5ba-b75befce8dd8", "--type", "gui"]

Stderr: VBoxManage: error: Host-only adapters are no longer supported!
VBoxManage: error: For your convenience a host-only network named 'Legacy  Network' has been created with network mask '255.255.255.0' and IP address range '192.168.56.1' - '192.168.56.254'.
VBoxManage: error: To fix this problem, switch to 'Host-only Network' attachment type in the VM settings.
VBoxManage: error:  (VERR_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Mac OS 14.6.1
Vagrant 2.4.1
Virtualbox 7.0.12r159484

Also, same result with Virtualbox 7.0.20r163906

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I messed it up and accidentally closed the pull request. The hostonlynet portion works only on a mac. https://www.virtualbox.org/ticket/21148

Not sure if there is a way to detect if it is on a mac and use hostonlynet and non mac to use hostonly.

@ttwd80 ttwd80 force-pushed the feature/ubuntu-24.04 branch from b6ffdaf to 2f30248 Compare September 7, 2024 19:10
@ttwd80 ttwd80 closed this Sep 7, 2024
@ttwd80 ttwd80 force-pushed the feature/ubuntu-24.04 branch from 2f30248 to 57faa62 Compare September 7, 2024 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants