AWS remove Leap 15.6 image and setup Leap 16.0#2203
Open
NamelessOne91 wants to merge 8 commits into
Open
Conversation
1 task
maximenoel8
approved these changes
Jul 12, 2026
NamelessOne91
force-pushed
the
aws_remove_leap_156_image
branch
2 times, most recently
from
July 15, 2026 12:38
68feedf to
b0b818f
Compare
NamelessOne91
force-pushed
the
aws_remove_leap_156_image
branch
from
July 16, 2026 12:34
b0b818f to
001ee66
Compare
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
2 participants
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.
What does this PR change?
Leap 15.6 is no longer available in AWS.
Our controller needs to use Leap 16.0 there, so the PR takes care of doing some setups for that too.
This involves:
Adding the possibility to use an arbitrary image for the controller instead of harcoding one. Leap 15.6 is still preserved as default.
Adding and handling the Sumaform and Uyuni tools repos for Leap 16.0
Leap 16.0 dropped the old network stack, so we need to check for netconfig to be actually available
apache2-mod_nssis not available in Leap 16.0. According to Gemini it should not be necessary for our needs also on old images, it was only used to setup some apache2 directories paths ---> needs to be properly checkedAdding healthcheck tool repo for Leap 16.0 - the proper one is not yet available, so we use Tumbleweed for the time being
Adding Ruby repositories for Leap 16.0 and the corresponding Ruby version