Refactor the usage of packages keyword in cloud-init, to avoid auto upgrade of packages #1702
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?
Don't upgrade packages in the systems deployed in a SUMA/Uyuni test environment.
The cloud team added the module
package-update-upgrade-install
to SUSE cloud-init configuration. This triggers an not-desired update of packages in some of the systems part of our test environment.This is triggered due to the usage of the keyword
packages
in our YAML file.This PR replace the keyword
packages
byruncmd zypper in
Example: