QA » openQA Project » openQA Tests » qe-yam

The qcow file SLES-12-SP5-ppc64le-GM-ids-idu-updated.qcow2 created from this test suite seems not used in migration.

A simply check done with this shell script:

function GET_ALL_QCOW() {
    local base_url='https://openqa.suse.de'
    local groupid='265'
    local flavor='Migration-from-SLE12-SPx'

    declare -a ids=(
        $(curl -k -X GET "${base_url}/api/v1/jobs/overview?groupid=${groupid}&flavor=${flavor}" 2>/dev/null | jq '.[].id')
    )

    declare -a ls_job_name=()

    for id in "${ids[@]}"; do
        json="$(curl -k -X GET "${base_url}/api/v1/jobs/${id}" 2>/dev/null)"
        HDD_1="$(echo $json | jq -r '.job.settings.HDD_1 | select( . != null)' )"
        [ -n "$HDD_1" ]  && printf 'HDD_1: %s\n' $HDD_1

        if [ "$HDD_1" == "SLES-12-SP5-ppc64le-GM-ids-idu-updated.qcow2" ]; then
            name="$(echo $json | jq -r '.job.name | select( . != null)' )"
            ls_job_name+=( $name )
        fi
    done

    for job_name in "${ls_job_name[@]}"; do
        echo "- used in: ${job_name}"
    done

}

GET_ALL_QCOW

show that the qcow is not in the list:

HDD_1: autoyast-SLES-12-SP5-x86_64-GM-all_patterns-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-ppc64le-HA-updated.qcow2
HDD_1: autoyast-SLES-12-SP5-aarch64-GM-all_patterns-updated.qcow2
HDD_1: SLES-12-SP5-x86_64-GM-SDK-allpatterns-uefi.qcow2
HDD_1: SLES-12-SP5-x86_64-GM-sdk-we-all_patterns-updated.qcow2
HDD_1: SLES-12-SP5-x86_64-GM-phub-updated.qcow2
HDD_1: autoyast-SLES-12-SP5-x86_64-GM-media-minimal-updated.qcow2
HDD_1: SLES-12-SP5-x86_64-GM-we-lp-updated.qcow2
HDD_1: autoyast-SLES-12-SP5-x86_64-GM-updated.qcow2
HDD_1: SLES-12-SP5-x86_64-GM-lp-asmm-contm-lgm-pcm-tcm-wsm-all_patterns-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-x86_64-HA-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-x86_64-HA-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-x86_64-SAP-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-x86_64-SAP-updated.qcow2
HDD_1: SLES-12-SP5-ppc64le-GM-lp-updated.qcow2
HDD_1: SLES-12-SP5-s390x-GM-lp-updated.qcow2
HDD_1: SLES-12-SP5-s390x-GM-sdk-lp-asmm-contm-lgm-pcm-tcm-wsm-all_patterns-updated.qcow2
HDD_1: autoyast-SLES-12-SP5-ppc64le-GM-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-s390x-HA-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-ppc64le-SAP-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-s390x-HA-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-ppc64le-SAP-updated.qcow2
HDD_1: SLES-12-SP5-ppc64le-GM-allpatterns-orig.qcow2
HDD_1: autoyast-SLES-12-SP5-s390x-GM-all_patterns-updated.qcow2
HDD_1: SLES-12-SP5-ppc64le-GM-lp-asmm-contm-lgm-pcm-tcm-wsm-all_patterns-updated.qcow2
HDD_1: autoyast_SLES-12-SP5-ppc64le-HA-updated.qcow2
HDD_1: SLES-12-SP5-aarch64-GM-sdk-pcm-tcm-wsm-all_patterns-updated.qcow2
HDD_1: autoyast-SLES-12-SP5-aarch64-GM-updated.qcow2

Remove scenario inside JobGroups/yast/yam_support_images_devel.yml, repo qam-openqa-yml

scenarios:
  ppc64le: 
     sle-12-SP5-Server-DVD-Updates-ppc64le:
     - sle_autoyast_support_image_gnome_12sp5_ids-idu:
         testsuite: null
         settings:
           START_AFTER_TEST: 'sle_autoyast_support_image_gnome_12sp5'
           DESKTOP: 'gnome'
           HDD_1: 'autoyast-SLES-%VERSION%-%ARCH%-GM-updated.qcow2'
           BOOT_HDD_IMAGE: '1'
           BETA: '0'
           PUBLISH_HDD_1: 'SLES-12-SP5-%ARCH%-GM-ids-idu-updated.qcow2'
           QEMU_VIRTIO_RNG: '0'
           +SCC_ADDONS: 'ids,idu'
           NO_ADD_MAINT_TEST_REPOS: '1'
           YAML_SCHEDULE: 'schedule/yam/create_support_image_module_combinations_updated.yaml'

Created MR#681

The qcow created in support image test https://openqa.suse.de/tests/13118169#settings used by migration milestone job https://openqa.suse.de/tests/13069765#settings, so no reason to remove the test suite.

Currently what we can do is to check the failure in the https://openqa.suse.de/tests/13118169 and check whether it is a new product bug.

I think we can reject this ticket now, currently migration test (target 15SP6) with ids,idu (http://openqa.nue.suse.com/tests/13120842#step/upgrade_select/6) will fail for https://bugzilla.suse.com/show_bug.cgi?id=1218244

These modules have migration packages, we can check this for a migration test (target 15SP5), https://openqa.suse.de/tests/13120846#step/installation_overview/3

leli wrote in #note-9:

I think we can reject this ticket now, currently migration test (target 15SP6) with ids,idu (http://openqa.nue.suse.com/tests/13120842#step/upgrade_select/6) will fail for https://bugzilla.suse.com/show_bug.cgi?id=1218244

These modules have migration packages, we can check this for a migration test (target 15SP5), https://openqa.suse.de/tests/13120846#step/installation_overview/3

Just to make up some info here: the two IBM modules for SLE 12 should migrate to another two IBM modules for SLE 15 here.
It only shows one IBM module migration path : Product IBM DLPAR Utils for SLE 12 will be updated to IBM POWER Tools for SLE 15 is a bug: https://bugzilla.suse.com/show_bug.cgi?id=1218250

The qcow file SLES-12-SP5-ppc64le-GM-ids-idu-updated.qcow2 created from this test suite is used in Migration: Milestone

A simply check done with previous shell script using:

    local groupid='266' # Migration: Milestone
    local flavor='Migration-from-SLE12-SPx-Milestone'

show that the qcow is in the list:

HDD_1: SLES-12-SP5-ppc64le-GM-ids-idu-updated.qcow2
HDD_1: SLES-12-SP5-aarch64-GM-sdk-pcm-tcm-wsm-all_patterns-updated.qcow2
HDD_1: SLES-12-SP5-x86_64-GM-we-lp-updated.qcow2
HDD_1: SLES-12-SP5-s390x-GM-sdk-lp-asmm-contm-lgm-pcm-tcm-wsm-all_patterns-updated.qcow2
HDD_1: SLES-12-SP5-ppc64le-GM-gnome.qcow2
HDD_1: SLES-12-SP4-x86_64-GM-gnome-allpatterns.qcow2
- used in: sle-15-SP6-Migration-from-SLE12-SPx-Milestone-ppc64le-Build44.1-offline_sles12sp5_rmt_ids-idu_def_full@ppc64le

Regarding AC1, it does makes sense to test this scenario, see Slack Thread Remaining part is AC2.