action #120444
closed
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Revisit wrong settings for HA migrations
Added by jgwang about 2 years ago.
Updated almost 2 years ago.
Description
Motivation¶
We should try to stick to the current configuration of the HA jobs, they should look the same, in the future we might figure out why some particular things are done in a way, but for now we can focus on matching the existing job behaviors. Things that we noticed:
- (1) Fix AutoYaST profiles to target multi-user instead of graphical, but it doesn't matter even if we write wrong the profile that the product takes precedence and use multi-user, but worth the fix to avoid confusion:
- (2) We are running HA migration in qt, instead of the original job that was doing in textmode: https://openqa.suse.de/tests/9917785 which is due to missing settings. In grub we should set the right video source.
- (3) Additionally license agreement is not shown for some addons https://openqa.suse.de/tests/9920480#step/addon_products_sle/30 but it is probably just wrong configuration, just comparing
SCC_ADDONS on similar job for older product in HA job group: https://openqa.suse.de/tests/9917785#settings, we might just need 'ha' instead of base,serverapp,ha
Acceptance criteria¶
AC1: Fix wrong configuration for HA migrations
Additional information¶
See #120106 for the mapping
- Tags set to qe-yast-refinement
- Subject changed from License agreement not shown for some addons to Revisit wrong settings for HA migrations
- Description updated (diff)
- Priority changed from Normal to Low
- Target version set to Current
i think ha standalone case use qt or text mode both ok.
Original ticket is use to clarify scenario: when you add ha or we addon, the license agreement should happen or not? If should show, then which situation will show?
Base current openqa code logic of addon_products_sle , it will show if you do fullcd without any register, so we need first understand the product requirement, then we trigger next step, either submit bug or change code.
- Description updated (diff)
- Description updated (diff)
- Tags deleted (
qe-yam-refinement)
- Status changed from New to Workable
- Related to action #120708: Update the default target of HA autoyast profile to make it flexible added
coolgw wrote:
Original ticket is use to clarify scenario: when you add ha or we addon, the license agreement should happen or not? If should show, then which situation will show?
Base current openqa code logic of addon_products_sle , it will show if you do fullcd without any register, so we need first understand the product requirement, then we trigger next step, either submit bug or change code.
we do some iterative process that when we have wrong configuration will give us that test error. Fixing addons setting should suffice. Behavior should be the same than the image we found there originally.
- Parent task set to #121876
- Status changed from Workable to In Progress
- Assignee set to tinawang123
- Status changed from In Progress to Resolved
Also available in: Atom
PDF