Project

General

Profile

Actions
Copy link

action #36451

closed

[functional][y] Testing presence or absence of update-test* packages on iso, based on BETA flag

Added by fcrozat almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
riafarov
Category:
New test
Target version:
SUSE QA - Milestone 19
Start date:
2018-05-23
Due date:
% Done:

0%

Estimated time:
8.00 h
Difficulty:

Description

Acceptance criteria

  • AC1: when BETA flag is set, the presence of update-test-32bit-pkg, update-test-32bit-pkg-32bit, 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, update-test-trivial package on the iso media / repository
  • AC2: when BETA flag is NOT set, those packages should NOT be available

Related issues 2 (1 open — 1 closed)

Related to openQA Tests - action #36313: [qe-core][sle][opensuse][qem] enhance update_packagekit testsWorkable2017-12-05

Actions
Related to openQA Tests - action #37288: [opensuse][caasp] test fails in transactional_update - Installation of update-test-broken-5-5.1.x86_64 failedResolvedmkravec2018-06-13

Actions
Actions
Copy link
 #1

Updated by okurz almost 6 years ago

  • Related to action #36313: [qe-core][sle][opensuse][qem] enhance update_packagekit tests added
Actions
Copy link
 #2

Updated by okurz almost 6 years ago

  • Subject changed from Testing presence or absence of update-test* packages on iso, based on BETA flag to [functional][y] Testing presence or absence of update-test* packages on iso, based on BETA flag
  • Category set to New test
  • Status changed from New to Feedback
  • Assignee set to okurz

@fcrozat Can the availability of packages be checked with "installcheck" or in IBS? We should not need a machine running in openQA for that, do we?

Actions
Copy link
 #3

Updated by fcrozat almost 6 years ago

okurz wrote:

@fcrozat Can the availability of packages be checked with "installcheck" or in IBS? We should not need a machine running in openQA for that, do we?

Installcheck only check consistency of the ISO, so it wouldn't work.

And the point of this test is to make sure we don't forget about adding / removing the packages, based on the product status. It is somehow similar to isosize check which was done in the past to some isos.

We would prefer to have this check integrated and visible in openQA dashboard.

Actions
Copy link
 #4

Updated by okurz almost 6 years ago

  • Description updated (diff)
  • Due date set to 2018-07-03
  • Status changed from Feedback to Workable
  • Assignee deleted (okurz)
  • Target version set to Milestone 17

Thanks for your fast feedback. Sure, this sounds feasible.

Actions
Copy link
 #5

Updated by okurz almost 6 years ago

  • Related to action #37288: [opensuse][caasp] test fails in transactional_update - Installation of update-test-broken-5-5.1.x86_64 failed added
Actions
Copy link
 #6

Updated by okurz almost 6 years ago

[13 Jun 2018 13:40:12] coolo: do you think something like https://progress.opensuse.org/issues/36451 is feasible to implement as a test not in openQA but rather in a more lightweight test in before?
[13 Jun 2018 14:06:41] okurz: I'm implementing a framework for doing such things within staging workflow for sp1. but fcrozat will want it for sp4
[13 Jun 2018 14:08:02] coolo: so you agree but say we won't have that before say … september?

Actions
Copy link
 #7

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 17
Actions
Copy link
 #8

Updated by riafarov almost 6 years ago

  • Status changed from Workable to In Progress
  • Assignee set to riafarov
Actions
Copy link
 #9

Updated by riafarov almost 6 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #10

Updated by JERiveraMoya almost 6 years ago

  • Estimated time set to 8.00 h
Actions
Copy link
 #11

Updated by riafarov almost 6 years ago

Added validation for SLE15, packages are expected to be in Basesystem as confirmed by Frederic.

Actions
Copy link
 #12

Updated by riafarov almost 6 years ago

VR for SLE 12 SP4: https://openqa.suse.de/tests/1791796#step/repo_package_install/1
As agreed with okurz, we keep ticket open until we get SLE15 build to validate test module there.

Actions
Copy link
 #13

Updated by okurz almost 6 years ago

  • Due date deleted (2018-07-03)
  • Target version changed from Milestone 17 to Milestone 19

right, so let's rechecke in M19 if we have a SLE15SP1 build by then, ok?

Actions
Copy link
 #15

Updated by michalnowak almost 6 years ago

I see problem with 'update-test-trivial' repo on SLES 12 SP4 JeOS https://openqa.suse.de/tests/1794515#step/repo_package_install/11.

Actions
Copy link
 #16

Updated by okurz almost 6 years ago

pcervinka wrote:

Is this failure on SLE15 correct https://openqa.suse.de/tests/1792509#step/repo_package_install/13?
Just started after https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5246

Interesting. Isn't the test behaving exactly like we want it to behave? The packages should not be there, see AC2, right? riafarov asked fcrozat also in #opensuse-factory.

michalnowak wrote:

I see problem with 'update-test-trivial' repo on SLES 12 SP4 JeOS https://openqa.suse.de/tests/1794515#step/repo_package_install/11.

Also interesting. Again, the test behaves as specified. The product does not set the beta flag and therefore the packages are not expected but of course SLE12SP4 is in development so @michalnowak as we are booting pre-generated JeOS images do you think it would work to just set the BETA flag for JeOS as well?

Actions
Copy link

Also available in: Atom PDF