Bugfix/68492 backports import#68760
Draft
harshang03 wants to merge 3 commits intosaltstack:masterfrom
Draft
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.
What does this PR do?
Ensures Salt can start without the optional backports package by injecting a minimal backports namespace (including an ssl_match_hostname fallback) early in startup and before loader module discovery.
What issues does this PR fix or reference?
Fixes #68492
Previous Behavior
Salt could fail to start in 3006 LTS environments where the backports package is missing, due to optional imports resolving the namespace at startup.
New Behavior
Salt sets up a minimal, safe backports namespace (and ssl_match_hostname fallback) during import and loader initialization so optional imports do not abort startup.
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
No