action #117127
closed
Run rebootmgr in transactional_server_helper_apps in PowerVM only in YaST development group
Added by rainerkoenig over 1 year ago.
Updated over 1 year ago.
Description
Motivation¶
As a result of openQA review SLE 15 SP5 Build 24.1:
Test rebootmgr is failing with the following message:
# Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host at /usr/lib/os-autoinst/testapi.pm line 1739.
During the whole previous SLES Service pack spent some time trying to figure out why this case doesn't work for PowerVM, but we didn't have the knowledge to go further after some research tickets. For that reason and given that Transactional features are more important for sle-micro or ALP than for SLE, we should keep running this test suite as it is in YaST Development Group in openQA and exclude this particular test modules (and the next if it is a dependency) in this test suite in YaST job group.
Acceptance criteria¶
AC1: Test module is excluded in YaST group (ID=129) and whole test suite run as it is in development group (ID=456)
Additional info¶
failed on SLE-15 SP4 GM
See related ticket for infrastructure issue.
Related issues
1 (1 open — 0 closed)
- Tags set to qe-yast-refinement
- Subject changed from Move transactional_server_helper_apps to YaST development group to Run transactional/rebootmgr in transactional_server_helper_apps only in YaST development group
- Description updated (diff)
- Target version set to Current
- Related to action #109112: Improve os-autoinst sshXtermVt.pm connection error handling (was: "Test died: Error connecting to <root@redcurrant-4.qa.suse.de>: No route to host") size:M added
- Description updated (diff)
- Description updated (diff)
- Subject changed from Run transactional/rebootmgr in transactional_server_helper_apps only in YaST development group to Run rebootmgr in transactional_server_helper_apps in PowerVM only in YaST development group
- Priority changed from Normal to High
AC1:
move transactional_server_helper_apps@ppc64le-hmc-single-disk to dev
no need exclude rebootmgr in YaST group (ID=129) since ONLY transactional_server_helper_apps@ppc64le-hmc-single-disk failed
- Tags deleted (
qe-yast-refinement)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to leli
So need two MRs for this, one is to remove it from yast group, another to add it to development group to avoid CI conflict.
We don't need to remove the test suite from YaST group, just exclude that module, and probably the next one, because they have a dependency, in YaST group.
In development group we run it as it is, without exclusion and we label with corresponding bug/progress ticket.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF