[ENHANCEMENT] Bump Harvester OS to SLE-Micro 5.5

[Vicente-Cheng]

Is your enhancement related to a problem? Please describe. We should use the newer OS for v1.4.0

Describe the solution you'd like Bump OS with SLE-Micro 5.5

Describe alternatives you've considered None

Additional context None

[innobead]

Have we considered bumping to SLE-Micro 5.6?

[Vicente-Cheng]

Have we considered bumping to SLE-Micro 5.6?

The next release of SLE-Micro 5.5 is SLE-Micro 6.0 (Ref: https://www.suse.com/lifecycle/#suse-linux-enterprise-micro)

IIUC, there are some major changes (like moving to btrfs instead image-based immutable OS) on SLE-Micro 6.0. So, I thought we should use SLE-Micro 5.5 instead SLE-MIcro 6.0. (6.0 will bring too many potential risks) Also, the EoL of SLE-Micro 5.5 is' 31 Oct 2027`. It's long enough for us to move on to the next.

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

~* [ ] If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted? The HEP PR is at:~

• [x] Where is the reproduce steps/test steps documented? The reproduce steps/test steps are at:

Test Plan: This is a base OS change, we can check the daily e2e test result to see any weird failure after that. Also, we can check the base OS version like below (with the installation from master-head ISO)

harvester-node-0:~ # cat /etc/os-release
NAME="SLE Micro"
VERSION="5.5"
VERSION_ID="5.5"
...

Make sure the NAME and VERSION look like the above.

~* [ ] Is there a workaround for the issue? If so, where is it documented? The workaround is at:~

• [x] Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)? The PR is at: OBS is update to date (REF: https://build.opensuse.org/package/show/isv:Rancher:Harvester:OS:Dev/baseos) https://github.com/harvester/harvester-installer/pull/757 https://github.com/harvester/os2/pull/113

  • [ ] Does the PR include the explanation for the fix or the feature?

  • [ ] Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart? The PR for the YAML change is at: The PR for the chart change is at:

~* [ ] If labeled: area/ui Has the UI issue filed or ready to be merged? The UI issue/PR is at:~

~* [ ] If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged? The documentation/KB PR is at:~

~* [ ] If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

• The automation skeleton PR is at:
• The automation test case PR is at:~

~* [ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility? The compatibility issue is filed at:~

[harvesterhci-io-github-bot]

Automation e2e test issue: harvester/tests#1336