action #157729
closed
coordination #151816: [epic] Handle openQA fixes and job group setup
Implement packages' vendor change in yast2 migration jobs
Added by zoecao 3 months ago.
Updated about 2 months ago.
Description
Motivation¶
We already implemented packages' vendor change in [offline migration cases] by adding setting of VENDOR_CHG_DEPS=1, still need to implement it for yast2 migration cases.
Here is the test result of yast2 migration case:
https://openqa.suse.de/tests/13845153#step/yast2_migration/15
I also set the VENDOR_CHG_DEPS=1 in the job, but it doesn't work because different with offline cases, here need to send key "down" to get "Packages" selected.
Testsuite name is online_sled15sp5_rmt_basesys-desktop-we-phub-python3_def_full_y and it is in milestone job groups.
Acceptance criteria¶
AC1 : Add setting of VENDOR_CHG_DEPS=1 and report results
AC2 : If existing mechanism doesn't work, purpose solutions.
It seems not the reason for not implement of vender change, but failed to deal with vendor change for a strange condition:
if (check_screen('manual-intervention', 0)) {
# In function deal_with_dependency_issues we handle different actions by VIDEOMODE,
# here we need change VIDEOMODE to something not text.
my $orig_videomode = get_var('VIDEOMODE', '');
set_var("VIDEOMODE", 'ssh-x');
$self->deal_with_dependency_issues;
set_var("VIDEOMODE", $orig_videomode);
}
Why need check_screen('manual-intervention', 0) to deal with vendor change? for my understanding the condition should change to check_screen('manual-intervention') then will continue to deal_with_dependency_issues. Need investigate more for the code history.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migr_sles15sp4_desktop_all
https://openqa.suse.de/tests/13931325#step/yast2_migration/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Tags set to qe-yam-apr-sprint
- Subject changed from To implement packages' vendor change in yast2 migration jobs to Implement packages' vendor change in yast2 migration jobs
- Status changed from New to Workable
- Parent task set to #151816
- Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
@zoecao is this still happening? could you please add latest result? I'm not sure if it is workable or not now...
- Status changed from Workable to In Progress
- Assignee set to tinawang123
- Priority changed from Normal to High
- Description updated (diff)
At 'deal_with_dependency_issues' function, it used 'tab' key to choose the expected menu:
send_key_until_needlematch 'packages-section-selected', 'tab';
But at our job: https://openqa.suse.de/tests/13845153#step/yast2_migration/15
It need use 'tab' key to choose the 'migration summary' part. then use 'down' key to choose the expected needle: 'packages-section-selected'
- Status changed from In Progress to Resolved
Also available in: Atom
PDF