secex: guard GPG encryption of Ignition config with mutex #3924
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Running secex tests with `--parallel=auto` complains: ``` $ cosa kola run --qemu-secex --tag secex --qemu-secex-hostkey hostkey.crt --parallel=auto === RUN ext.config.shared.secex.ensure === RUN ext.config.shared.secex.reboot 2024-11-01T17:28:29Z kola: retryloop: failed to bring up machines: encrypting /var/tmp/mantle-qemu2551463228/ignition_crypted.1734631171: exit status 2 ``` Use mutex for `gpg --encrypt` to avoid this issue.
nikita-dubrovskii
force-pushed
the
gpg_issue
branch
from
8065f61
to
749ca68
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running secex tests with
--parallel=autocomplains:Use mutex for
gpg --encryptto avoid this issue.