Project

General

Profile

action #55097

[SLE][Migration][SLE12SP5]: Check 12sp5 Jira issue and implement automation version check(phase2)

Added by coolgw about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2019-08-05
Due date:
% Done:

100%

Estimated time:
20.00 h
Difficulty:

Description

Phase2 for jira issue check(12sp5):
SLE-5708 -QA: Add python-daemon to the distributionBLOCKED Should Have(New add 05 Aug 2019 ) python-daemon, can be checked after migration Can check python-daemon after migration
SLE-5584 -QA: rsync update to at least 3.1.3BLOCKED Should Have(New add 05 Aug 2019 ) check rsync  version

SLE-6817 -QA: dpdk package for SLES 12 SP4 BLOCKED Should Have(New add 05 Aug 2019 ) check dpdk version

SLE-6820 -QA: frequently updated dpdk package to deliver together with the Azure kernel BLOCKED Should Have(New add 05 Aug 2019 ) check dpdk package version

SLE-5668 -QA: Replace init script of ebtables with systemd service fileBLOCKED Should Have(New add 05 Aug 2019 ) can check start ebtable after Replace init script of ebtables with systemd service file


Related issues

Related to openQA Tests - action #54257: [SLE][Migration][SLE12SP5]: Check 12sp5 Jira issue and implement automation version checkResolved2019-07-15

History

#1 Updated by coolgw about 3 years ago

  • Related to action #54257: [SLE][Migration][SLE12SP5]: Check 12sp5 Jira issue and implement automation version check added

#2 Updated by coolgw about 3 years ago

  • Estimated time changed from 16.00 h to 20.00 h

#3 Updated by tinawang123 about 3 years ago

Martin suggestion:

After upgrade, check that versions of packages in upgreaded system match those present - there is list of packages present on installation media in path_to_installer/DVD1/ls-lR.gz

Check if there are no orphaned packages in system - zypper packages --orphaned

#4 Updated by tinawang123 about 3 years ago

Sebastian suggestion:
If anything such perl code could help with one thing - generic check of given packages versions.
So I would consider such approach:
test should have a variable, "RPM_LIST", so that the tester could provide comma-delimited packages with expected versions and the test would check that and provide well-formated output file with actual rpm version and expected ones.

If such stuff is provided this could be useful.

Better yet - instead hard to maintain potentially long list of comma-delimited rpms, provide a functionality to supply test with external csv file or something like that.

In such case you would provide a generic lib/functions for such generic rpm version checks and then use this generic function in your test.pm script.

#5 Updated by coolgw about 3 years ago

  • Assignee set to tinawang123

#6 Updated by coolgw almost 3 years ago

  • Priority changed from High to Normal

#7 Updated by tinawang123 almost 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

#8 Updated by tinawang123 almost 3 years ago

Need feedback about https://jira.suse.com/browse/SLE-5708 (Check how to check python-daemon)
and
https://jira.suse.com/browse/SLE-5754 (Check version should be fixed or not)

#9 Updated by tinawang123 almost 3 years ago

  • % Done changed from 70 to 90

Need verify run.

#11 Updated by tinawang123 almost 3 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF