Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix static SLES version to use facts #2554

Closed
wants to merge 0 commits into from

Conversation

pascalseeland
Copy link

Summary

SUSE release SLES15 SP6, which causes a wrong module path when upgrading from SP5 to SP6.

This patch uses the major and minor number provided by factor to create the correct paths

Additional Context

Add any additional context about the problem here.

  • Root cause and the steps to reproduce. (If applicable)

With the upgrade from 15.5 to 15.6 the path of the module needs to be changed. Otherwise the module tries to enable a 15.5 repo on 15.6 which fails with

Notice: /Stage[main]/Apache::Mod::Php/Exec[enable legacy repos]/returns: 
Notice: /Stage[main]/Apache::Mod::Php/Exec[enable legacy repos]/returns: Activating sle-module-legacy 15.5 x86_64 ...
Notice: /Stage[main]/Apache::Mod::Php/Exec[enable legacy repos]/returns: Error: Registration server returned 'The product you are attempting to activate (Legacy Module 15 SP5 x86_64) requires one of these products to be activated first: Server Applications Module 15 SP5 x86_64' (422)
Error: 'SUSEConnect --product sle-module-legacy/15.5/x86_64' returned 67 instead of one of [0]
Error: /Stage[main]/Apache::Mod::Php/Exec[enable legacy repos]/returns: change from 'notrun' to ['0'] failed: 'SUSEConnect --product sle-module-legacy/15.5/x86_64' returned 67 instead of one of [0] (corrective)
  • Thought process behind the implementation.

Related Issues (if any)

Mention any related issues or pull requests.

Checklist

  • 🟢 Spec tests.
  • 🟢 Acceptance tests.
  • Manually verified. (For example puppet apply)

@CLAassistant
Copy link

CLAassistant commented Jul 6, 2024

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants