Project

General

Profile

Actions

action #9464

closed

coordination #15108: [sle][functional][u][epic] Modules (Installation + migration)

[sle][functional][u] Modules - Advanced Systems Management

Added by RBrownSUSE over 8 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
SUSE QA - Milestone 26
Start date:
2018-12-12
Due date:
2019-06-04
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

We require proper modules testing

This should be done as part of Validation if possible

ASM Module should test the following

  • Installation of

    • puppet
    • cfengine
    • machinery
    • salt
  • Basic functionality of (ie. Does the application start and do one or two common functions)

    • puppet
    • cfengine
    • machinery
    • salt
  • optional: Broad coverage of the functionality of Puppet, CFEngine, and Machinery, etc.


Checklist

  • SLE

Subtasks 2 (0 open2 closed)

QA - action #45080: [sle][functional][u] test machineryResolveddheidler2018-12-122019-02-08

Actions
QA - action #45083: [sle][functional][u] test cfengineRejectedmgriessmeier2018-12-122019-06-04

Actions

Related issues 1 (0 open1 closed)

Related to openQA Tests - action #18604: [sles][functional]gnome-asmm-proxySCC test fails in consoletest_setup due invalid repositoryResolvedokurz2017-04-18

Actions
Actions #2

Updated by RBrownSUSE over 8 years ago

  • Subject changed from sle12 - modules - Advanced Systems Management to Modules - Advanced Systems Management
Actions #3

Updated by RBrownSUSE over 8 years ago

  • Checklist item changed from to [ ] SLE
  • Target version deleted (156)
Actions #4

Updated by okurz over 7 years ago

  • Parent task set to #15108
Actions #5

Updated by asmorodskyi about 7 years ago

  • Related to action #17042: [sles][functional][modules] Modules installation added
Actions #6

Updated by asmorodskyi about 7 years ago

  • Related to deleted (action #17042: [sles][functional][modules] Modules installation)
Actions #7

Updated by dgutu about 7 years ago

In the related task Oliver tried to enable and install the module by using ProxySCC but it does not apper in the patterns.
At least it appears in the Product List on the installation settings step(review page before perform the installation itself)

Actions #8

Updated by okurz about 7 years ago

[18 Apr 2017 14:46:44] anja: ok, let's come back to this issue at best tomorrow then
[18 Apr 2017 15:02:58] who added the scenario "gnome-asmm-proxySCC" to functional server? Please add a "maintainer" and make sure it works first before adding something to "Functional: Server"

so it was you, dgutu ;-) I removed the test suite again as it is not working, never was and is incomplete. I recommend the following approach:

  • use manual triggering with "jobs post" and necessary settings and see that it works at least once
  • add test suite and enable it in development group
  • if it works consistently there, enable it in "Functional: Server"

Only add something to the validation job groups after it has been proven to work.

Actions #9

Updated by okurz about 7 years ago

  • Related to action #18604: [sles][functional]gnome-asmm-proxySCC test fails in consoletest_setup due invalid repository added
Actions #10

Updated by dgutu almost 7 years ago

By not reinventing the testcase I started to check and test the one Oliver wrote.
I'm surprised that this very basic test can't pass successfully.
The error is "Minion did not return. [No response]"

Actions #11

Updated by dgutu almost 7 years ago

dgutu wrote:

By not reinventing the testcase I started to check and test the one Oliver wrote.
I'm surprised that this very basic test can't pass successfully.
The error is "Minion did not return. [No response]"

The issue description doesn't include Salt, should I ignore it for now?

Actions #12

Updated by dgutu almost 7 years ago

  • Assignee set to dgutu
Actions #13

Updated by okurz almost 7 years ago

  • Category deleted (New test)

IMHO we should also cover salt, especially because we already have a salt test running in openSUSE openQA tests.

When you want to continue working on this ticket I still strongly recommend you go step by step and complete first one simple test (including having it running in production), then continue to the next. Just start with the easiest module, does not need to be salt at first.

Actions #14

Updated by maritawerner almost 7 years ago

  • Category set to New test
Actions #15

Updated by dgutu almost 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20
Actions #16

Updated by dgutu almost 7 years ago

  • Assignee changed from dgutu to okurz
Actions #17

Updated by okurz almost 7 years ago

  • Description updated (diff)
  • Assignee deleted (okurz)
Actions #18

Updated by okurz almost 7 years ago

  • Subject changed from Modules - Advanced Systems Management to [sle][functional]Modules - Advanced Systems Management
Actions #19

Updated by okurz over 6 years ago

  • Target version set to Milestone 14
Actions #20

Updated by riafarov over 6 years ago

  • Status changed from In Progress to Workable
Actions #21

Updated by okurz about 6 years ago

  • Due date set to 2018-03-13
Actions #22

Updated by okurz about 6 years ago

  • Due date changed from 2018-03-13 to 2018-04-24
  • Target version changed from Milestone 14 to Milestone 15

This gets more relevant for SLE12 SP4 again and we are quite busy fixing SLE15 stuff so let's postpone a bit.

Actions #23

Updated by mgriessmeier about 6 years ago

  • Subject changed from [sle][functional]Modules - Advanced Systems Management to [sle][functional][u] Modules - Advanced Systems Management
Actions #24

Updated by okurz about 6 years ago

  • Due date deleted (2018-04-24)
  • Target version changed from Milestone 15 to Milestone 17

Sprint 15 is too full with new test already and with every "new test" we break something so let's not overdo it ;)

Actions #25

Updated by okurz almost 6 years ago

  • Due date set to 2018-07-17
  • Status changed from Workable to Blocked
  • Assignee set to okurz
  • Priority changed from Normal to Low

before we go further here I would like to see results from https://bugzilla.suse.com/show_bug.cgi?id=1092498 about puppet not being available on SLE and potentially moved to packagehub as this impacts how we want to test other components.

Actions #26

Updated by okurz almost 6 years ago

  • Subject changed from [sle][functional][u] Modules - Advanced Systems Management to [sle][functional][u][bsc#1092498] Modules - Advanced Systems Management
Actions #27

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 17
Actions #28

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 18
Actions #29

Updated by okurz almost 6 years ago

  • Due date changed from 2018-07-17 to 2018-08-14

It's hackweek time!

Actions #30

Updated by okurz over 5 years ago

  • Due date changed from 2018-08-14 to 2018-12-18
  • Target version changed from Milestone 18 to Milestone 21

No update in ticket

Actions #31

Updated by okurz over 5 years ago

  • Due date changed from 2018-12-18 to 2019-12-31
  • Target version changed from Milestone 21 to Milestone 25+

no movement in bug

Actions #32

Updated by okurz over 5 years ago

  • Subject changed from [sle][functional][u][bsc#1092498] Modules - Advanced Systems Management to [sle][functional][u] Modules - Advanced Systems Management
  • Target version changed from Milestone 25+ to Milestone 23

I closed bsc#1092498 as RESOLVED WONTFIX after we finally got an answer from Joe :)

Created two specific subtasks for cfengine and machinery, blocked by subtasks.

Actions #33

Updated by okurz over 5 years ago

  • Due date set to 2019-02-08

due to changes in a related task

Actions #34

Updated by okurz about 5 years ago

  • Due date changed from 2019-02-08 to 2019-02-26

due to changes in a related task

Actions #35

Updated by okurz about 5 years ago

  • Due date changed from 2019-02-26 to 2019-02-08

due to changes in a related task

Actions #36

Updated by okurz about 5 years ago

  • Due date changed from 2019-02-08 to 2019-03-26

due to changes in a related task

Actions #37

Updated by okurz about 5 years ago

  • Due date changed from 2019-03-26 to 2019-06-04

due to changes in a related task

Actions #38

Updated by okurz about 5 years ago

  • Target version changed from Milestone 23 to Milestone 25

-> #45083

Actions #39

Updated by okurz almost 5 years ago

  • Assignee changed from okurz to mgriessmeier

Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.

Actions #40

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions #41

Updated by maritawerner almost 5 years ago

  • Status changed from Blocked to Resolved

All subtasks are done. Set it to resolved.

Actions

Also available in: Atom PDF