Project

General

Profile

action #36313

[sle][opensuse][qam] enhance update_packagekit tests

Added by jorauch about 2 years ago. Updated 3 months ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Enhancement to existing tests
Target version:
Start date:
2017-12-05
Due date:
% Done:

0%

Estimated time:
5.00 h
Difficulty:
medium
Duration:

Description

Observation

In the update tests we depend highly on which types of updates are available, so we do not test every branch in every build (e.g. we have no updates that require a reboot)
To test as much as possible there are update tests in: http://download.opensuse.org/update/leap/15.0/oss/x86_64/
We should try to integrate this to our tests, not only for leap but for all products

Acceptance criteria

AC1: Tests are not broken
AC2: All sorts of updates are being tested on opensuse
AC3: All sorts of updates are being tested on sle

Suggestions

  • Do not test updates on openSUSE Tumbleweed because updates there are less important and seldom and we do not have an update repo with test packages
  • For SLE or Leap make sure that the published update-repo with test update packages (see #36451) are available, at least as long as BETA=1 is set

Related issues

Related to openQA Tests - action #36451: [functional][y] Testing presence or absence of update-test* packages on iso, based on BETA flagResolved2018-05-23

Blocked by openQA Tests - action #38393: [functional][u] updates_packagekit_kde must not be scheduled before zypper_clear_reposResolved2018-07-132018-08-14

Copied from openQA Tests - action #28875: [sle][functional][sporadic][hard][u] test fails in updates_packagekit_gpk - updater should not be started when already runningResolved2017-12-052018-05-22

History

#1 Updated by jorauch about 2 years ago

  • Copied from action #28875: [sle][functional][sporadic][hard][u] test fails in updates_packagekit_gpk - updater should not be started when already running added

#2 Updated by jorauch about 2 years ago

  • Status changed from Feedback to Workable
  • Priority changed from High to Normal

#3 Updated by okurz about 2 years ago

  • Priority changed from Normal to Low
  • Target version changed from Milestone 16 to Milestone 18

It's a cool idea but that high prio for now. So sure, you can continue to work on this as a fall-back task for now and eventually we should also pick it up with higher prio again.

#4 Updated by jorauch about 2 years ago

  • Priority changed from Low to Normal
  • Target version changed from Milestone 18 to Milestone 16

The question here is at wich point we should add the new repo.
I would do this in a seperate module to keep it flexible enough for all products and architectures
Maybe we could use zypper_ar for this

#5 Updated by okurz about 2 years ago

  • Related to action #36451: [functional][y] Testing presence or absence of update-test* packages on iso, based on BETA flag added

#6 Updated by okurz about 2 years ago

did you change the prio + milestone intentionally?

#7 Updated by jorauch about 2 years ago

  • Priority changed from Normal to Low
  • Target version changed from Milestone 16 to Milestone 18

Nope, that happened when adding the last comment, sorry for that

#8 Updated by okurz almost 2 years ago

  • Target version changed from Milestone 18 to Milestone 18

#9 Updated by jorauch almost 2 years ago

  • Due date set to 2018-08-14

As discussed with okurz

#11 Updated by mgriessmeier almost 2 years ago

  • Blocked by action #38393: [functional][u] updates_packagekit_kde must not be scheduled before zypper_clear_repos added

#12 Updated by mgriessmeier almost 2 years ago

  • Status changed from Workable to Blocked

#13 Updated by mgriessmeier almost 2 years ago

  • Estimated time set to 5.00 h

#14 Updated by okurz almost 2 years ago

  • Description updated (diff)

#15 Updated by okurz almost 2 years ago

  • Status changed from Blocked to Workable

blocker resolved. I think this covers "do not look for updates on TW" already. If in doubt talk to dheidler please.

#16 Updated by okurz almost 2 years ago

  • Due date changed from 2018-08-14 to 2018-08-28

bulk move to next sprint as could not be discussed in SR

#17 Updated by okurz almost 2 years ago

  • Due date changed from 2018-08-28 to 2018-09-11
  • Target version changed from Milestone 18 to Milestone 19

we got interrupted on that one for the time being. We have too many tickets planned for current S24 so let's delay some time

#18 Updated by jorauch almost 2 years ago

I would like to delay this until the return of dheidler

#19 Updated by mgriessmeier over 1 year ago

  • Due date changed from 2018-09-11 to 2018-09-25

#20 Updated by mgriessmeier over 1 year ago

  • Due date changed from 2018-09-25 to 2018-10-09
  • Assignee deleted (jorauch)

#21 Updated by okurz over 1 year ago

  • Due date deleted (2018-10-09)
  • Target version changed from Milestone 19 to future

riafarov is currently working on harmonizing the update schedule which might have an impact and someone from QAM plans to look into update_packagekit_kde as well. We can look into this but … not now.

#22 Updated by mgriessmeier 3 months ago

  • Status changed from Workable to Rejected

We don't know currently what parts of this is already covered and what not - please reopen or create a proper one with explicit request

#23 Updated by okurz 3 months ago

  • Subject changed from [sle][opensuse][functional][medium][u] enhance update_packagekit tests to [sle][opensuse][qam] enhance update_packagekit tests
  • Status changed from Rejected to Workable

mgriessmeier wrote:

We don't know currently what parts of this is already covered and what not - please reopen or create a proper one with explicit request

this is a bit lame explanation. The link to test updates needs an update of course: http://download.opensuse.org/update/leap/15.2/oss/x86_64/

This shows all different categories of updates:

  • update-test-32bit-pkg
  • update-test-affects-package-manager
  • update-test-broken
  • update-test-feature
  • update-test-interactive
  • update-test-optional
  • update-test-reboot-needed
  • update-test-relogin-suggested
  • update-test-security
  • update-test-trivial

but I think by now it fits better the scope of [qam].

Also available in: Atom PDF