Project

General

Profile

Actions

action #44144

closed

[functional][y] Rework "boot_into_snapshot" to boot from images and not reconduct whole installation

Added by okurz over 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 26
Start date:
2018-11-21
Due date:
2019-07-16
% Done:

0%

Estimated time:
3.00 h
Difficulty:

Description

Motivation

Currently we conduct a full installation just to boot into a snapshot afterwards. We should rewrite the test to boot published images and try booting into snapshots there
This will help us to signficantly reduce execution time of the test suite.

Here is the scenario for SLE 12 SP 5: https://openqa.suse.de/tests/latest?version=12-SP5&arch=x86_64&machine=64bit&distri=sle&test=boot_to_snapshot&flavor=Server-DVD

Acceptance criteria

  1. Pre-created image is used to test functionality to boot into the image

Suggestion

We consider migrating scenario to yaml if schedule is same for all architectures, then we should be able to avoid using BOOTHDD parameter.


Related issues 2 (0 open2 closed)

Related to openQA Tests - coordination #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job groupResolvedriafarov2018-10-252019-11-19

Actions
Blocks openQA Tests - action #43064: [functional][u] test fails in boot_into_snapshot and reboot_gnome with encrypted setup - test not waiting long enough for shutdown/reboot until we end up in grub which shows in post_fail_hookResolvedmgriessmeier2018-10-30

Actions
Actions #1

Updated by okurz over 5 years ago

  • Blocks action #43064: [functional][u] test fails in boot_into_snapshot and reboot_gnome with encrypted setup - test not waiting long enough for shutdown/reboot until we end up in grub which shows in post_fail_hook added
Actions #2

Updated by okurz over 5 years ago

  • Blocked by coordination #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group added
Actions #3

Updated by okurz over 5 years ago

  • Status changed from New to Blocked
  • Target version changed from Milestone 21 to Milestone 22
Actions #5

Updated by okurz about 5 years ago

  • Target version changed from Milestone 22 to Milestone 25
Actions #6

Updated by okurz almost 5 years ago

  • Assignee changed from okurz to riafarov

Move to new QSF-y 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-y. Feel free to reassign to me or someone else in this case. Thanks.

Actions #7

Updated by riafarov almost 5 years ago

  • Description updated (diff)
  • Due date set to 2019-07-02
  • Status changed from Blocked to Workable
  • Assignee deleted (riafarov)
  • Target version changed from Milestone 25 to Milestone 26
Actions #8

Updated by riafarov almost 5 years ago

  • Blocked by deleted (coordination #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group)
Actions #9

Updated by riafarov almost 5 years ago

  • Related to coordination #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group added
Actions #10

Updated by riafarov almost 5 years ago

  • Estimated time set to 3.00 h
Actions #11

Updated by riafarov almost 5 years ago

  • Description updated (diff)
Actions #12

Updated by riafarov almost 5 years ago

  • Due date changed from 2019-07-02 to 2019-07-16
Actions #13

Updated by oorlov almost 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to oorlov
Actions #14

Updated by oorlov almost 5 years ago

  • Status changed from In Progress to Feedback
Actions #15

Updated by okurz almost 5 years ago

  • Priority changed from Normal to Urgent

PR was merged. I can see the change effective on o3 however seems we are missing a START_AFTER_TEST, see https://openqa.opensuse.org/tests/973347#

Actions #16

Updated by oorlov almost 5 years ago

I've added the START_AFTER_TEST to yaml file, but it is incorrect, as this variable is required by the scheduler. So, it should be removed from the yaml file and defined in the Test Suite menu of openQA.

I've added the appropriate parameter on both o3 and osd and retriggered the job on o3: https://openqa.opensuse.org/tests/974189.

Actions #17

Updated by okurz almost 5 years ago

Please take a look into the according aarch64 failure as well: https://openqa.opensuse.org/tests/974192

Actions #18

Updated by okurz almost 5 years ago

Also I guess you should simplify the existing schedules by e.g. deleting the schedule parts about the boot_into_snapshot part when this is handled with a YAML schedule.

Actions #19

Updated by oorlov almost 5 years ago

The test failed on aarch64, because UEFI_PFLASH_VARS=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%-uefi-vars.qcow2 was not specified in Test Suite settings.

Regarding removing the boot_into_snapshot test module from main.pm, there is a weird part. The test module was skipped for a year, though the test suite was executed every build. Due to

sub snapper_is_applicable {
    # run snapper tests on opensuse only for system_performance testsuite
    return 0 if (is_opensuse && !get_var('SOFTFAIL_BSC1063638'));
...

I'll discuss with the team on what we plan to do with the test suite and the module, as now it is not clear for me.

Actions #20

Updated by oorlov almost 5 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF