Fix Alloy sysext SHA256 hash #82
Merged
Conversation
This file contains hidden or 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
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.
Summary
Fixes Ignition failure caused by Alloy sysext SHA256 hash mismatch.
The hash changed after the build process was migrated to the separate alloy-sysext-build repository.
Old hash:
feb76c5aa5408c267d59508bd39d322c20d6fce44abd686296f4d0ca87e42671New hash:
a0db1a966874eac9284dde47fb0cd917fdef22088701409f98d5e2e7fd70ae0fTest plan
systemctl status alloyshows running