Network and SSH problems using bento/ubuntu-20.04-arm64 and bento/ubuntu-22.04-arm64 with Vagrant #1473
Comments
|
@sford, thanks for your info, I will test this next week. Enjoy the weekend |
|
Hello @sford, it is indeed the same. Does anybody knows when the images are going to be updated? Thanks! |
|
Beginning of march I plan to update the images. Hoping to keep a quarterly cadence. With the new hcl rewrite and dedicated builders for testing I’m currently working on getting the builds stable and working. Most x86_64 builds are working for virtualbox, parallels, and VMware, but aarch64, hyperv, and qemu machines still have a bit of tweaking needed to get builds working. |
|
With that, any testing and fixes you may find, if you can submit PR’s for them that’ll be greatly appreciated. |
|
Hi, thanks for the reply. When I find something I will certainty look at it. |
|
Can someone test one of these images to verify it fixes the issues you guys are seeing? If so then I can work on getting them officially published. https://github.com/chef/bento/actions/runs/4328485365#artifacts |
|
Sure, but I need some help how to test the aarch64 Ubuntu 22.10, how do I specify this image in the Vagrant file? |
|
If you download the image you want to test then you can use the vagrant box add command and give it a name like test/ubuntu-version and point to the downloaded file. Then in your vagrant file you’d set the image to the name you gave it. |
|
Hi, I have done it, it is picking up the new box, but I do get an error, when changing some SSH parameters, FYI, this is working in 20.04: BTW, this is a config with only 1 vm in it. Maybe something changed in Ubuntu regarding SSH or something corrupt? https://codetryout.com/failed-to-restart-sshd-service-unit-sshd-service-not-found/ |
|
Hi, testing with 22.10, 4 vm's, gives problems: This is with 20.04, working: This is with 22.10, I only changed the box in the config, failing: it times out |
|
Thanks. What do you get with testing 22.04? I know starting with 22.04 and rhel 9 based machines they finally removed the old ssh key algorithms based on sha1 and less than 2048 bits. Since that was the old default it requires users to generate new ssh keys for auth. I’m not sure if there are any other ssh changes that would be affecting the service. |
|
Your output for working 20.04 box is that based on new version from the PR build yet to be released or is that old version that is currently in vagrant cloud? |
|
It is the one in Vagrant Cloud |
I will test it with 22.04 today, give me a few hours |
|
With 22.04 same problem as with 22.10: |
|
Can you try the 20.04 release in the linked build job? Want to rule out OS ssh changes or Bento build script changes. |
|
Hi, the 20.04 in the linked build job is working correctly |
|
ok thanks, since all versions are running the same scripts/setup that means it probably has to do with dropping of old ssh algorithms. Can you see if updating your keys or adding to the sshd_config for weak ciphers fixes your issue for you. This article explains it pretty well. https://askubuntu.com/questions/1409105/ubuntu-22-04-ssh-the-rsa-key-isnt-working-since-upgrading-from-20-04. Thanks again for all the help testing. |
|
Hi @Stromweld, this is probably the wrong place to document since I am not using Some more details... I am using Here are logs showing I also ran our test suite on these VMs. We configure them with Puppet (sorry chef!) and run our tests. Everything passed and didn't run into any problems. Thanks @Stromweld ! |
Hi, it is logging in with the Vagrant user, so I guess it is using an self generated keypair. For my own keypair, I have exactly done as written in your link, but that is for my own user. Log: |
|
@sford Thanks for letting me know. Glad to hear that's fixed. @Evantage-WS Thanks for all the testing. I'll try to dig into it some more and see if I can figure out the issue/fix. |
|
Great, thanks |
|
Hi @Stromweld, I do see a new release, is the problem I reported fixed so I can test it? |
|
There hasn't been a new release of the Vagrant Ubuntu boxes for Arm architecture yet. I'm hoping to get those built by the end of this week. |
|
Ok, thanks. |
Turns out the issue with duplicate DHCP address is an issue with the cox itself in chef/bento#1473
|
I don't have a working ubuntu-20.04-arm64 box yet, but there is the 22.04-arm box with the fixes mentioned above. Does this fit the need and does this box also fix the dhcp issue https://app.vagrantup.com/bento/boxes/ubuntu-22.04-arm64? |
|
Hi @Stromweld, just a quick test, unfortunally the same problem: |
|
I believe this is actually a vagrant issue and should be fixed in the latest version of vagrant with the ssh key algorithm fix https://github.com/hashicorp/vagrant/blob/v2.3.7/CHANGELOG.md I also just released new builds of 20.04-arm64 and 22.04-arm64. Can you confirm this is working for you now? |
|
Hi @Stromweld, Thanks, I have upgraded Vagrant and updated my sources to use the newly created box, but when using it I do get an EFI_RNG_PROTOCOL unavailable error. When using the 20.04 image, it is working fine, so it think it is something in the newly created image |
|
Both boxes are working for me. Please check that your vagrant files are the same. Closing this issue. Please feel free to open a new issue or reopen this issue if problems are found with boxes or code. |
Version
bento/ubuntu-20.04-arm64 v202301.20.0
Environment
Vagrant 2.3.4
Scenario
Installing multiple vm's and randomly failing with login into vm with the vagrant ssh key at the vm creating stage, eventually it will time out with vagrant up.
As stated, it happens randomly, so when a login is succesful into a vm, it happens a lot that the internal networking remains working (172.16.0.0/24), but the internet connection is working for about a minute, then unreachable for 5 minutes or more, every time at a different stage in my Vagrantfile. I use multiple shell provisioners.
This all happens with the 202301.20.0 version. When using the 202112.19.0 version it all works fine, every time.
Steps to Reproduce
You need to setup multiple vm's and use a couple of shell provisioners and download data. In my case there are helm charts and apt packages.
Expected Result
With 202301.20.0 the same result as using 202112.19.0
Actual Result
Tried it 11 times, it fails all the time with 202301.20.0, tested it 4 times with 202112.19.0, 4 times succesful. I also tried it with bento/ubuntu-22.04-arm64, but the same login problems rise. I was unable to get to the shell provisioners part at my 2 tests with bento/ubuntu-22.04-arm64.
The text was updated successfully, but these errors were encountered: