QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

In migration job group build59.1, the ha conflict is caused by non-added ltss for 15sp5:
https://openqa.suse.de/tests/16639459#step/patch_sle/81
Already verified that the issue will not be reproducible if adding ltss:
VR: [support image]; [migration]
So I submit a MR to add ltss to all 15sp5 scenarios:
https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/411

Slack: https://suse.slack.com/archives/C02CLB2LB7Z/p1738750196367349

The MR to add ltss to 15SP5 support images and migration testsuites was merged.
Triggered the related jobs, found some of support images testsuites still need further changes for their ay profile:
For example testsuite: supp_sles15sp5, its's profile hardcode the modules as:

  <suse_register t="map">
    <addons t="list">
      <addon t="map">
        <arch>{{ARCH}}</arch>
        <name>sle-module-python3</name>
    <version>{{VERSION}}</version>
      </addon>
      <addon t="map">
        <arch>{{ARCH}}</arch>
        <name>sle-module-server-applications</name>
        <version>{{VERSION}}</version>
      </addon>
      <addon t="map">
        <arch>{{ARCH}}</arch>
        <name>sle-module-basesystem</name>
        <version>{{VERSION}}</version>
      </addon>
    </addons>

so even if the ltss is added to SCC_ADDONS setting, it is still not registered during installation. Need to update the profile as below:

  <suse_register>
    <do_registration config:type="boolean">true</do_registration>
    <email/>
    <reg_code>{{SCC_REGCODE}}</reg_code>
    <install_updates config:type="boolean">true</install_updates>
    <reg_server>{{SCC_URL}}</reg_server>
    % if (keys %$addons) {
    <addons config:type="list">
        % while (my ($key, $addon) = each (%$addons)) {
        <addon>
            <name><%= $addon->{name} %></name>
            <version><%= $addon->{version} %></version>
            <arch><%= $addon->{arch} %></arch>
            % if ($key eq 'we' and $check_var->('SLE_PRODUCT', 'sles')) {
            <reg_code><%= $get_var->('SCC_REGCODE_WE') %></reg_code>
            % }
            % if ($key eq 'ltss') {
            <reg_code><%= $get_var->('SCC_REGCODE_LTSS') %></reg_code>
            % }
            % if ($key eq 'ha') {
            <reg_code><%= $get_var->('SCC_REGCODE_HA') %></reg_code>
            % }
        </addon>
        % }
    </addons>
    %}

The following testsuites need to be updated:

• supp_sles15sp5
• supp_sles15sp5_all
• supp_sles15sp5_desktop_all
• supp_sles15sp5_desktop

For all arches of x86_64, s390x and aarch64.

Submit a PR to add ltss to sles15sp5 testsuites, checked the sles15sp4 ay profiles, add ltss as:

<addon t="map">
  <arch>{{ARCH}}</arch>
  <name>SLES-LTSS</name>
  <version>{{VERSION}}</version>
  <reg_code>{{SCC_REGCODE_LTSS}}</reg_code>
</addon>

And I found some sles15sp6 support images testsuites are also using sles15sp5 ay profiles, but 15SP6 is not into ltss yet, so create ay profiles for those sles15sp6 testsuites.
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21143
VRs: [sles15sp5]; [sles15sp6]

And related MR: https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/413