-
Notifications
You must be signed in to change notification settings - Fork 33
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
Flatcar fails to install current (GPG signature check failed) #1163
Comments
I have now tried the following combinations: stage-0 (current) & to-install (current): stage-0 (3227.2.2) & to-install (3227.2.2): stage-0 (3227.2.2) & to-install (current): |
That's expected, 3510.2.6 is the latest Stable version and the outdated 3227.2.2 doesn't have the key. A workaround for old images would be to first download |
We use 3227.2.2 primarly since it has undergone lots of internal testing. |
flatcar-install also supports supplying the gpg key to use for verification. https://github.com/flatcar/init/blob/flatcar-master/bin/flatcar-install#L105 |
Description
flatcar-install
fails to install flatcar, using the "stable" release channel and the "current" version.The error occurs due to a missing public key for the image signer (
[email protected]
@E9426D8B67E35DF476BD048185F7C8868837E271
)Impact
This bug prevents us and our customers from installing our stack, in all cases where we use "stable"/"current" instead of our pinned older version (3227.2.2).
Environment and steps to reproduce
flatcar-install -d /dev/sda -C stable -V current -v
is enough to replicate the bug.a. Our iPXE chainloads 3227.2.2 as stage-0
b. stage-0 executes
flatcar-install -d /dev/sda -C stable -V current -v
Expected behavior
The key for the most recent stable version should be valid and available.
Additional information
stage-0 /etc/os-release
Install output (this is from a manual start, instead of the service, but the error remains the same):
The text was updated successfully, but these errors were encountered: