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

Error : "end of file before message length reached" #199

Closed
fclerg opened this issue Mar 27, 2020 · 1 comment
Closed

Error : "end of file before message length reached" #199

fclerg opened this issue Mar 27, 2020 · 1 comment

Comments

@fclerg
Copy link

fclerg commented Mar 27, 2020

Bug

Host Operating System Version

Proxmox 5.2-12

Target Operating System Version

fedora-coreos-31.20200210.3.0

coreos-installer Version

coreos-installer 0.1.2

Expected Behavior

Successful installation of CoreOS

Actual Behavior

coreos-installer-error

The relevant part seems to be :
Caused by: end of file before message length reached

Reproduction Steps

PXE boot. Here is my iPXE config (it is provided by Matchbox to match a configuration with a machine):

	"boot": {
		"kernel": "http://10.20.30.100:8000/image/fedora-coreos-31.20200210.3.0-live-kernel-x86_64",
		"initrd": [
			"http://10.20.30.100:8000/image/fedora-coreos-31.20200210.3.0-live-initramfs.x86_64.img"
		],
		"args": [
			"ip=dhcp",
			"rd.neednet=1",
			"initrd=fedora-coreos-31.20200210.3.0-live-initramfs.x86_64.img",
			"coreos.inst.image_url=http://10.20.30.100:8000/image/fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz",
			"coreos.inst.ignition_url=http://matchbox.yuzu.local:8080/ignition?uuid=${uuid}\u0026mac=${mac:hexhyp}",
			"coreos.inst.install_dev=sda",
                        "coreos.inst.insecure=yes",
                        "random.trust_cpu=on",
			"console=tty0",
                        "systemd.journald.max_level_console=debug"
		]
	}

Other Information

After it fails I can access the emergency mode for maintenance.
From there I could confirm that the guest gets its IP config with DHCP and that it has access to the internet.
I didn't find anything obvious about the failure. I am not sure where to look at, based on this "end of file before message length reached" error message.

The image I use is fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz.
I use a copy of the image in a local web repo and I can confirm its signature and integrity :

# gpg --verify fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz.sig  fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz
gpg: Signature made Mon Feb 24 18:03:55 2020 UTC using RSA key ID 3C3359C4
gpg: Good signature from "Fedora (31) <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 7D22 D586 7F2A 4236 474B  F7B8 50CB 390B 3C33 59C4
#
# curl -s https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/31.20200210.3.0/x86_64/meta.json \
>   | jq -r '.images.metal | select(.path=="fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz") | .sha256'
8ed20e48375ea2c0c09dace2a06d366d80990f97f2a79757dbc81078424725c6
# sha256sum  fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz
8ed20e48375ea2c0c09dace2a06d366d80990f97f2a79757dbc81078424725c6  fedora-coreos-31.20200210.3.0-metal.x86_64.raw.xz
#
@dustymabe
Copy link
Member

duplicate of coreos/fedora-coreos-tracker#439 where we've got some conversations going on already so let's close this.

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

No branches or pull requests

2 participants