-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unable to generate secure boot ISO with custom kernel args #104
Labels
bug
Something isn't working
Comments
smira
added a commit
to smira/talos
that referenced
this issue
Apr 10, 2024
Previous approach relied on a field which is _only_ present if file-based PKI is passed in, and fails for e.g. Azure KMS. See siderolabs/image-factory#104 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira
added a commit
to smira/talos
that referenced
this issue
Apr 10, 2024
Previous approach relied on a field which is _only_ present if file-based PKI is passed in, and fails for e.g. Azure KMS. See siderolabs/image-factory#104 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira
added a commit
to smira/talos
that referenced
this issue
Apr 10, 2024
Previous approach relied on a field which is _only_ present if file-based PKI is passed in, and fails for e.g. Azure KMS. See siderolabs/image-factory#104 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira
added a commit
to smira/image-service
that referenced
this issue
Apr 10, 2024
Fixes siderolabs#104 Pull in Talos with a fix siderolabs/talos#8571 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira
added a commit
to smira/talos
that referenced
this issue
Apr 12, 2024
Previous approach relied on a field which is _only_ present if file-based PKI is passed in, and fails for e.g. Azure KMS. See siderolabs/image-factory#104 Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com> (cherry picked from commit 909a580)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Generating a secureboot ISO works fine with the default schematic, but when I add custom kernel args (e.g.
talos.experiment.wipe=system
) the secureboot ISO fails to generate.schematic ID:
9acd4f2454d4969f5351e85d824eb5d27f8124b56d281d8a03c924fa1a7cfd2f
The standard ISO download works, but the secureboot ISO download fails.
The text was updated successfully, but these errors were encountered: