action #36021

[functional][u][epic] add test to verify default packages

Added by lnussel almost 2 years ago. Updated 12 months ago.

Status:ResolvedStart date:09/05/2018
Priority:NormalDue date:
Assignee:okurz% Done:

100%

Category:New test
Target version:QA - future
Difficulty:
Duration:

Description

boo1092408 reports that accidentally the wrong default MTA was installed. We should have a test hat verifies the correct choices of services that have alternatives are installed


Subtasks

action #43346: [functional][u] add test to verify default packages - net...Resolveddheidler

History

#1 Updated by lnussel almost 2 years ago

  • Description updated (diff)

#2 Updated by okurz almost 2 years ago

  • Subject changed from add test to verify default packages to [functional][u] add test to verify default packages
  • Description updated (diff)
  • Category set to New test
  • Target version set to Milestone 19

How can we know what are the expected correct choices? Or should we just take the current ones as default and whenever the product defaults are changed intentionally then adjust the test?

#3 Updated by okurz over 1 year ago

  • Target version changed from Milestone 19 to Milestone 19

#4 Updated by okurz over 1 year ago

  • Status changed from New to Rejected
  • Assignee set to okurz

no response

#5 Updated by lnussel over 1 year ago

  • Status changed from Rejected to New

yes

#6 Updated by okurz over 1 year ago

  • Status changed from New to Workable
  • Assignee deleted (okurz)
  • Target version changed from Milestone 19 to future

alright, works for me.

#7 Updated by okurz over 1 year ago

  • Status changed from Workable to New

Bulk action to set status back to "New" for older tickets which are in "future". They would need to be revisited in time when we come up with a defined plan and assign to a milestone.

#8 Updated by lnussel over 1 year ago

current example: https://lists.opensuse.org/opensuse-factory/2018-10/msg00318.html
Here we have both chrony and ntpd installed but neither enabled. A test would have to check both.

#9 Updated by okurz over 1 year ago

  • Copied to action #43052: [functional][u] add test to verify default packages - chrony added

#10 Updated by okurz over 1 year ago

  • Subject changed from [functional][u] add test to verify default packages to [functional][u][epic] add test to verify default packages

Alright, created #43052 to handle chronie/ntp specifically. I found that tests/caasp/services_enabled.pm already does this check but for caasp only :(

So after chronie/ntp, should we just have another ticket for the default MTA? Anything else?

#11 Updated by lnussel over 1 year ago

syslog
and another incident reminded me of NetworkManager vs wicked.

#12 Updated by okurz over 1 year ago

  • Description updated (diff)

#13 Updated by okurz over 1 year ago

  • Copied to deleted (action #43052: [functional][u] add test to verify default packages - chrony)

#14 Updated by okurz over 1 year ago

  • Description updated (diff)

#15 Updated by dheidler over 1 year ago

Currently this testmodules get scheduled in the extra_tests_textmode testsuite.

Maybe we could at the end move all this testmodules into a separate testsuite.

#16 Updated by okurz 12 months ago

  • Status changed from New to Resolved
  • Assignee set to okurz

the mentioned tickets and subtasks are done. Since the last comment we have split the "extra tests" further so also the schedule should be easier to understand.

Also available in: Atom PDF