action #37531
closed
[sle][functional][y] PCM patterns cause package installation conflicts but these use cases are unsupported anyway
Added by zluo about 6 years ago.
Updated about 6 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 18
Description
Compared with previous successful test run, I can see there is something changes here: GCC 5 Compiler
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-ppc64le-allmodules+allpatterns@ppc64le fails in
select_patterns_and_packages
Reproducible¶
Fails since (at least) Build 0256
Expected result¶
Last good: 0256 (or more recent)
Further details¶
Always latest result in this scenario: latest
https://bugzilla.suse.com/show_bug.cgi?id=1008985 has an explanation as well, e.g.
it's not supported to install all public cloud patterns in parallel, as this doesn't reflect any meaningful usecase. You can install all patterns of one Cloud Service Provider, e.g. Microsoft Azure, but even that does not really make sense as the installed packages cover very different use cases. For instance one pattern is only useful on an instance running in the public cloud, etc.
- Related to coordination #37114: [functional][y][epic] Enable automated testing of "public cloud providers" (PCM) explicitly added
- Subject changed from [sle][functional][y] test fails in select_patterns_and_packages - needle 'current-pattern-selected' not matched to [sle][functional][y][fast] PCM patterns cause package installation conflicts but these use cases are unsupported anyway
- Status changed from New to In Progress
- Assignee set to okurz
- Priority changed from Normal to High
- Target version set to Milestone 17
- Due date set to 2018-07-03
- Subject changed from [sle][functional][y][fast] PCM patterns cause package installation conflicts but these use cases are unsupported anyway to [sle][functional][y] PCM patterns cause package installation conflicts but these use cases are unsupported anyway
- Due date deleted (
2018-07-03)
- Status changed from In Progress to Feedback
- Priority changed from High to Low
- Target version changed from Milestone 17 to Milestone 19
Seems tests can work without this so my assumption was wrong. Let's discuss this over time, no need to rush. Latest allmodules+allpatterns is fine.
- Description updated (diff)
- Priority changed from Low to Normal
- Target version changed from Milestone 19 to Milestone 18
- Status changed from Feedback to Resolved
scenario should be fine by now. Since then with the work on #37114 and its subtickets we have specific test scenarios for each cloud provider.
Also available in: Atom
PDF