QA

https://gitlab.suse.de/qa-maintenance/templates-management/-/issues/31

Starting with 15.3, openSUSE Leap uses identical binary packages as SLES if the source is shared, both for installation and updates.
Starting 2021-06-24 a change was put in place how these binary packages are channeled to the openSUSE 15.3 update repositories. From that date on, the incident project configuration (project.xml) for SLE updates might contain sections like this:

  <repository name="SUSE_Updates_openSUSE-SLE_15.3">
    <releasetarget project="SUSE:Updates:openSUSE-SLE:15.3" repository="update" trigger="maintenance"/>
    <path project="SUSE:Updates:openSUSE-SLE:15.3" repository="update"/>
    <arch>i586</arch>
    <arch>x86_64</arch>
    <arch>s390x</arch>
    <arch>ppc64le</arch>
    <arch>aarch64</arch>
  </repository>

Since we don't want to manually re-validate SLE updates on openSUSE outside of openQA, we need to make sure that the template generator is skipping over such releasetarget definitions and doesn't try to create a product definition or a list of reference test machines from it.
Currently, we got 1 error and 1 warning from the template generator on such incidents:

2021/06/23 18:01:30 W SUSE:Maintenance:20182:243591 QAM.TeReGen.Input.OBS: Ignoring "SUSE:Updates:openSUSE-SLE:15.3" - not representing any known product
2021/06/23 18:01:30 E SUSE:Maintenance:20182:243591 QAM.TeReGen.Input.OBS: Cannot parse version from SUSE_Updates_openSUSE-SLE_15.3

The test reports currently generated and look good, e.g. https://qam.suse.de/testreports/SUSE:Maintenance:20182:243591/log
However, we need to make sure for the future that the release target SUSE:Updates:openSUSE-SLE:15.3 is excluded more gracefully / intentionally by the template generator.