Project

General

Profile

action #33940

[sle][functional][sle15][y] Add existing test suite "allmodules+allpatterns" to s390x/ppc64le/aarch64

Added by okurz about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Start date:
2018-03-28
Due date:
2018-05-08
% Done:

0%

Estimated time:
Difficulty:
Duration: 30

Description

Motivation

We have added a new test suite "allmodules+allpatterns" and scheduled for SLE15 on x86_64. As modules and patterns differ per architecture and can also cause problems there I guess it makes sense to have according scenarios enabled for s390x/ppc64le/aarch64 as well

Acceptance criteria

  • AC1: passing/soft-failing scenario allmodules+allpatterns enabled for SLE15 for all architectures or excluded for good reasons

Suggestion

  • Add scenario for all missing architectures to SLE15 test development
  • Review all test results after at least one build was scheduled with these tests enabled
  • Potentially remove scenarios where it does not make sense to have them
  • Create needles or slightly adjust test code where needed, e.g. to enable and according module/pattern list in the test code

Related issues

Blocked by openQA Tests - action #33937: [sle][functional][12sp4][y] Add existing test suite "allmodules+allpatterns" to SLE12SP4 scheduleResolved2018-03-282018-05-08

History

#1 Updated by okurz about 2 years ago

  • Copied from action #33937: [sle][functional][12sp4][y] Add existing test suite "allmodules+allpatterns" to SLE12SP4 schedule added

#2 Updated by okurz about 2 years ago

  • Copied from deleted (action #33937: [sle][functional][12sp4][y] Add existing test suite "allmodules+allpatterns" to SLE12SP4 schedule)

#3 Updated by okurz about 2 years ago

  • Blocked by action #33937: [sle][functional][12sp4][y] Add existing test suite "allmodules+allpatterns" to SLE12SP4 schedule added

#4 Updated by mgriessmeier about 2 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from Milestone 15 to Milestone 16

#5 Updated by okurz about 2 years ago

  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)

Blocking ticket resolved, can be picked up

#6 Updated by JERiveraMoya about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya

#7 Updated by JERiveraMoya about 2 years ago

Scheduled in group "Development: SLE 15" and before next build arrives, cloned to check results: https://openqa.suse.de/tests/1666535 https://openqa.suse.de/tests/1666554 https://openqa.suse.de/tests/1666555

#8 Updated by JERiveraMoya about 2 years ago

It looks good. Moved scheduling of the tests from "Development: SLE 15" group to "Functional".

#9 Updated by okurz about 2 years ago

Only that the tests do not actually enable "all modules".

IMHO https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/products/sle/main.pm#L204 needs to be tweaked. Please consult with jorauch, the testsuite maintainer, how to continue. Added him as watcher.

#10 Updated by jorauch about 2 years ago

Not sure what to consult here?
Just add the other modules and be happy

#11 Updated by JERiveraMoya about 2 years ago

I see, it is because I tried to build it using to clone the all-patterns test suite as base. More reliable results are in openQA group "Development: SLE 15": https://openqa.suse.de/tests/1666643 and https://openqa.suse.de/tests/1666879 which were scheduled by triggering the build, not manually by me. Both results resemble what we have for x86_64. I think in the manual cloning I missed ENABLE_ALL_SCC_MODULES. The other point is that the x86_64 does not click in all the modules. We are selecting Basesystem + Server Applications + content of SCC_ADDONS variable "legacy,sdk,pcm,wsm,contm,desktop". jorauch, do we need to select remaining unselected modules, for instance SUSE Enterprise Storage 6, etc. ?

#12 Updated by okurz about 2 years ago

That looks way better. Please enable phub (package hub) on both aarch64 and ppc64le

#13 Updated by JERiveraMoya about 2 years ago

  • Status changed from In Progress to Feedback

#14 Updated by JERiveraMoya about 2 years ago

  • Status changed from Feedback to Resolved

#15 Updated by okurz about 2 years ago

  • Due date changed from 2018-05-08 to 2018-05-22
  • Status changed from Resolved to Workable
  • Assignee deleted (JERiveraMoya)
  • Priority changed from Normal to Urgent

[9 May 2018 10:12:29] something has caused https://openqa.suse.de/tests/1676538#step/puppet/6 to fail now. The module was not scheduled in the previous build and I could not find related changes in the test code
[9 May 2018 10:18:41] okurz: phub was added to SCC_ADDONS
[9 May 2018 10:20:07] hm, ok. Thought that would have been in before already, ok
[9 May 2018 10:20:43] I diffed vars.json from 609.1 to 600.1 - and that's the only obvious change
[9 May 2018 10:21:38] yes, explains it of course because puppet is only enabled if phub is in
[9 May 2018 10:24:15] jrauch: didn't you add phub to the SCC_ADDONS variable for the all modules scenario?
[9 May 2018 10:25:00] ah, no. it was jrivera
[9 May 2018 10:25:03] okurz: I didnt touch anything, thought jrivera was working on this?

So we need to fix this.

#16 Updated by okurz about 2 years ago

  • Due date changed from 2018-05-22 to 2018-05-08
  • Status changed from Workable to Resolved
  • Assignee set to JERiveraMoya
  • Priority changed from Urgent to Normal

ok, fine. let's handle this new failure in #36024

Also available in: Atom PDF