action #161225
closedcoordination #152771: [epic] Add migrations in maintenance using AutoYaST
Provide migration from SLES 12 SP5 to SLES 15 SP5 in aggregated updates
0%
Updated by tinawang123 7 months ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by tinawang123 7 months ago ยท Edited
- Status changed from In Progress to Blocked
Reported one bug: https://bugzilla.suse.com/show_bug.cgi?id=1226677
Related job: https://openqa.suse.de/tests/14701785
Updated by JERiveraMoya 6 months ago
- Tags changed from qe-yam-jun-sprint to qe-yam-jul-sprint
- Status changed from Blocked to In Progress
hi @tinawang123 could you please give another try here? I think all the bugs are resolved.
For next time, please use Status "New" as we decided to not use Blocked (and we might loose track of the problem a bit as has happened).
Updated by tinawang123 6 months ago
The issue still can be reproduced
Refer: https://openqa.suse.de/tests/14856840#step/installation/84
I reopened the bug
I cannot set the ticket status to 'New'
Updated by JERiveraMoya 6 months ago
Now https://bugzilla.suse.com/show_bug.cgi?id=1226930 is fixed. Let's give it a try again.
Updated by tinawang123 6 months ago
The duplicate bug didn't fix my problem
The bug still can reproduce:
Refer job: https://openqa.suse.de/tests/14979875#step/installation/84
Added the comment to my bug: https://bugzilla.suse.com/show_bug.cgi?id=1226677
Updated by rainerkoenig 5 months ago
- Tags changed from qe-yam-jul-sprint, qe-yam-aug-sprint to qe-yam-aug-sprint
Updated by zoecao 5 months ago
To update the status here, the case is still blocked by [the bug].
Test result: https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&build=20240804-1&groupid=576
The bug was marked as resolved, so I checked the related fix in maintenance, the fix is planed to release at 2024-08-16.
Updated by zoecao 5 months ago
The fixed package version is not released to SLES15SP5, so the issue is still reproducible:
https://openqa.suse.de/tests/15209968#
I reopened the bug: https://bugzilla.suse.com/show_bug.cgi?id=1226930
Updated by JERiveraMoya 5 months ago
- Tags changed from qe-yam-aug-sprint to qe-yam-sep-sprint
- Status changed from In Progress to Workable
Updated by zoecao 4 months ago
- Status changed from Workable to In Progress
Found the reason why the bug always reproduced in VRs: https://openqa.suse.de/tests/15526343#next_previous
The upgrade autoyast profile didn't open the "receive update" flag during upgrading, the migration target product didn't receive the latest updates.
I open the "receive update" flag in profile, and it seems the VR is pass:
https://openqa.suse.de/tests/15526343#live
Will submit PR and MR for this ticket when the VR finishes.
Updated by JERiveraMoya 4 months ago
- Tags changed from qe-yam-sep-sprint to qe-yam-oct-sprint
Updated by zoecao 4 months ago
I opened the receive update flag in autoupgrade profile by adding:
<install_updates config:type="boolean">true</install_updates>
and the bug is gone, submit PR and MR for this ticket:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20269
https://gitlab.suse.de/qe-yam/openqa-job-groups/-/merge_requests/334
Updated by zoecao 3 months ago
- Status changed from In Progress to Resolved
PR and MR are merged, and the added testuiste is working well:
https://openqa.suse.de/tests/15553241
Resolve here now, thanks.