QA » openQA Project » openQA Tests » qe-yam

JERiveraMoya wrote in #note-2:

Please @hjluo continue with your current ticket #154948 before picking another new migration in maintenance because this kind of tasks have certain complexity.
It is more efficient as a team to run them in parallel by different assignee, I hope you agree, let me know otherwise please.
Besides by design this task is completely different that the other one, because in one we add the unrelease maintenance updates in origin and here in target.

I'm picking it up just because my ticket #154948 was done and now it's just a few lines' effort to add a test and run the VR.

Learning Huajian's PR and VRs, and added testsuites of migration to SLES15SP5 for this ticket, will trigger the jobs.

I used the SLES12SP5 image published from support image group, boot the image and register the system then upgrade it to SLES15SP5+ MU_unreleased_updates by autoyast profile.
Please correct me if I made it wrong, thanks.

Added a yaml_schedule file & an upgrade autoyast profile by PR, and running the verification:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=20240314-1&groupid=251
Still may need to adjust the yaml_schedule file and testsuites settings.

@JERiveraMoya I update result here:
This is the latest test results: https://openqa.suse.de/tests/13790232#
I checked whether the 15-SP5 MU repos are added or not by checking the [clone-installedSystem.xml], found that only part of MU repos are added when doing migration. And the reason is that I set +SCC_ADDONS=sdk,we,contm to the testsuite. If let the case add all of MU repos, we need to set +SCC_ADDONS=MRU_ADDONS (that is we,sdk,base,script,serverapp,desktop,legacy,contm,python3), but we can not do this in this case because the job boot SLES12SP5 image and register SLES12SP5 first, while on SLES12SP5, there's no such modules like base,serverapp,python3.
So to make the migration job involve all of the 15SP5 MU repos, I will divide the one migration job to two: One is to boot SLES12SP5 image and register the system (SCC_ADDONS=sdk,we,contm); the second one is to do migration and set SCC_ADDONS=MRU_ADDONS.
WDYT? or any other solutions for this?

I divided the one migration job to two, and triggered the jobs:
12SP5 register: https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&build=20240318-1&groupid=251
15SP5 migration: https://openqa.suse.de/tests/overview?state=assigned&state=setup&state=running&state=uploading&state=scheduled&distri=sle&version=15-SP5&build=20240318-1&groupid=251
WIll check the results later.

BTW, I have test to add MU repos manually in local VM, after migration, the MU repos are in the repo list when doing "zypper lr". SO I will continue to check why the autoyast profile didn't work in my VR.

zoecao wrote in #note-9:

I divided the one migration job to two, and triggered the jobs:
12SP5 register: https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&build=20240318-1&groupid=251
15SP5 migration: https://openqa.suse.de/tests/overview?state=assigned&state=setup&state=running&state=uploading&state=scheduled&distri=sle&version=15-SP5&build=20240318-1&groupid=251
WIll check the results later.

BTW, I have test to add MU repos manually in local VM, after migration, the MU repos are in the repo list when doing "zypper lr". SO I will continue to check why the autoyast profile didn't work in my VR.

feel free to ask developers is that is even supported (add addon of the TARGET product (be clear about that, not the ORIGIN product, I remember the confusion last time we asked this) during autoyast upgrade), perhaps there is some AutoYaST bug, take into account they will tell you that that is not the way a customer will test it, but this is the way we add the unrealeased maintenance updates in QE, each repo as an addon, we need a way to do that or we cannot use autoyast. Does the unified installed allow you to add addons products during interactive installation? then it should be possible to do it with auto-installation, you can verify that as well.

To update status of this ticket:
This is the latest test result for this ticket:
12SP5 register: https://openqa.suse.de/tests/13871204
15SP5 migration: https://openqa.suse.de/tests/13871208#
But MU repos are not added during migration, I already asked the question, I haven't got the answer yet.

To make the question more clearer, I created an interactive migration with additional addons repos added:
https://openqa.suse.de/tests/13872548#step/add_update_test_repo/118
and send it to help-yast channel for developers to understand the question.

Based on developer's requirement, I provided jobs with Y2DEBUG disabled to make the saved log shorter:
https://suse.slack.com/archives/C02D1T4S58S/p1711429081013739
And this is the job which works for disabling Y2DEBUG finally:
https://openqa.suse.de/tests/13906900#
Then need to wait for developer's debug for the issue (the MU repos are not in installed during migration).

I submit PR and MR for this ticket:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18932
https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/139
And please no rush to merge them, just in case any troubles caused by them, but comments are welcomed, thanks.
Still need to file a bug report to trace the AutoYaST upgrade issue, will do it after public vacation.

Switch the testsuite to use AutoYaST, and fixing the PR based on the comments, this is new verification run:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=20240409-1&groupid=251

zoecao wrote in #note-15:

Switch the testsuite to use AutoYaST, and fixing the PR based on the comments, this is new verification run:
https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=20240409-1&groupid=251

Let's keep the conversation in github, verification do not make much more sense in progress if the PR/MR is not merged (unless there is some doubt or blocking point for example, also Slack can be used for that).
We need to see the changes in the code and the verification updated there to analyze the result. Could you please update the PR according to that?