Open BuhtigithuB opened 2 years ago
The previous logs were coming from Windows Host, the above screenshot is with Linux Ubuntu 20.04 and VB 6.1.32_Ubuntu r149290
I attempted with windows and linux to ssh in the running installer instance of the to be linux image box, it seems to initiate the ssh communication as you can see in the attached screenshot but when I input the "vagrant" password it fails misirably...
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 : https://github.com/boxcutter/ubuntu/issues/196#issuecomment-755405452 @nrundle mention that it might be related to ssh_handshake_attempts
delay that should be longer then the subiquity process to complete or packer will attempt to ssh in the ssh instance of the installer which is not intiated and defined by packer which will trigger the installation to fails... So I tried with longer delay up to 600...
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.
apt:
geoip: false
@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 \
[-only=
It is not clear what version
variable does, my guess is to label created build with different names/versions?
It lets me timestamp the artifacts, with an option to build more than one artifact per day by incrementing n {1,2,3,etc}
That's what I thought...
Saddly it seems to fail on the same issue :
Is vagrant required to build packer box??
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...
https://github.com/hashicorp/packer/issues/8609
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: Explicitly specify a mirror in user-data:
apt:
geoip: false
primary:
- arches: [default]
uri: "http://mirrors.vcea.wsu.edu/ubuntu"
--force-yes
Force yes; this is a dangerous option that will cause apt to continue without
prompting if it is doing something potentially harmful. It should not be used except
in very special situations. Using force-yes can potentially destroy your system!
Configuration Item: APT::Get::force-yes.
But figure out how to set that in user-data. https://curtin.readthedocs.io/en/latest/topics/apt_source.html
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:
vm_name = "ubuntu2204"
iso_checksum = "sha256:39fdd5f7e868ab7981b492a8887dbaec85acf798b209162a37893cb4b209a26b"
iso_url = "http://releases.ubuntu.com/22.04/ubuntu-22.04-beta-live-server-amd64.iso"
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" iso_url = "http://releases.ubuntu.com/20.04/ubuntu-20.04-4-live-server-amd64.iso"
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