-
Notifications
You must be signed in to change notification settings - Fork 375
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
Ubuntu 20.04 subiquity log #207
Comments
DEBUG] SSH handshake err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain This error is suppose to come from ssh key and password missmatch : Here : #196 (comment) @nrundle mention that it might be related to Otherwise the network interface adapter has the right name, I check even it was a concern only for vmware : |
I was messing around with all this back in August and got the subiquity install completed. I have a commit where I increased ssh_handshake_attempts from 20 to 200. |
1649282298.894723177.install_fail.crash.zip I extracted the crash report joined here... Hopefully someone with more knowledge than I will make sens of all this :D |
Probably unrelated but I also added the following to user-data, to prevent hanging.
|
@polobo, I am trying it right now, there is like 3 differents places the handshake attempts can be set... I put all of them to 200... |
Yeah, I basically started a fork for my limited needs that I could mess with, removing and reworking quite a few things, so a simple share of my changes is less useful (at least without more research on my end). For reference I got it to work with the following versions:
|
It crashed again.. |
@polobo can you push you hacked branch on your clone... You don't need to make PR just reference your moded branch here with might flag something doing some diff... I know this whole thing is often version sensitive... |
Nice @polobo, you made a lot of improvement using hcl... I will test it, after I try the current repo with packer 1.7.4 |
Same old with 1.7.4... Trying your repo now... |
@polobo, you have a small typo not closing double quote in the readme.md packer build It is not clear what |
It lets me timestamp the artifacts, with an option to build more than one artifact per day by incrementing n {1,2,3,etc} |
Is vagrant required to build packer box?? |
I've never tried this particular process without it, and haven't tried any other packer using process either... My interest is piqued but no guarantees I'm going to be able to dive in deep anytime soon. |
vagrant was installed, so my issue doesn't come from there... I never used vagrant to build boxcutter ubuntu image box... |
openssh 8.2+ on my system |
I'm getting the same problem when I try the 20.04-4 ISO. I unable to experiment further right now but I basically have two thoughts:
But figure out how to set that in user-data. Maybe enabling geoip again, assuming the hang doesn't resume, will fix this new issue? I'm also curious if the 22.04 beta exhibits the same problem. Toward that end:
I did re-run the 20.04-2 build with my cached ISO and it worked just fine. |
I added the primary block to the apt block in the user-data and that didn't change anything. But removing the entire apt block got me past the subiquity initialization portion and a successful build using: iso_checksum = "sha256:28ccdb56450e643bad03bb7bcf7507ce3d8d90e8bf09e38f6bd9ac298a98eaad" Same software architecture I showed earlier, though the error seems to exist within the iso itself so I'm doubtful software versions for the other components matter. |
Hi,
I saw the other opened issue... But none report full extensive log output... Here my debug output :
I try many thing like making sure the encrypted password here https://github.com/boxcutter/ubuntu/blob/master/http/user-data#L6 is "vagrant"...
I tweak network section as describe here : https://ubuntu.com/server/docs/install/autoinstall-reference
(2 network keys)
I had ssh PasswordAuthentication yes here : https://github.com/boxcutter/ubuntu/blob/master/script/sshd.sh
(even if I think this happen later in the process)
I change the image reference 20.04.4 is now the up to date version and the old image is not available at the same URL
20.04.2 : https://old-releases.ubuntu.com/releases/20.04.2/ubuntu-20.04.2-live-server-amd64.iso
20.04.4 : http://www.releases.ubuntu.com/20.04/ubuntu-20.04.4-live-server-amd64.iso
The text was updated successfully, but these errors were encountered: