[SLE15-SP6] Better summary for the SLE_HPC => SLES upgrade (jsc#PED-7841) #652
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.
Problem
Related to SLE HPC is not a base product anymore (jsc#PED-7841) #650, https://jira.suse.com/browse/PED-7841
The display product summary at a SLE_HPC upgrade was not perfect:
That is technically correct, but it actually is SLE_HPC => SLES base product upgrade/migration and the HPC module upgrade to a newer version
Solution
Technical Details
Originally it was
"SLE_HPC" => ["SLES", "sle-module-hpc"]
mapping. But because the old SLE_HPC required the HPC module (a hard dependency, you cannot have SLE_HPC without the HPC module) then the real upgrade is not "SLE_HPC => SLES + HPC" but rather "SLE_HPC + HPC => SLES + HPC". And in that case we can remove the HPC module from the mapping because it will be automatically upgraded to the new available version.If the HPC module was optional for SLE_HPC we would have to add it to the mapping, but as it was mandatory we can leave it out.
That mapping is used when finding the product upgrades for the upgrade summary. The extra HPC value confuses the algorithm and it thinks the SLE_HPC is upgraded to the HPC module.
Testing