Project

General

Profile

Actions

action #129535

closed

[security][15-SP4] test fails in swtpm_env_setup

Added by amanzini 11 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-05-18
Due date:
% Done:

100%

Estimated time:
Difficulty:
Tags:

Description

Observation

openQA test in scenario sle-15-SP4-Server-DVD-Updates-x86_64-security_swtpm@64bit fails in
swtpm_env_setup

Test suite description

Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.

Reproducible

Fails since (at least) Build 20230517-1

Expected result

Last good: 20230516-1 (or more recent)

Further details

Always latest result in this scenario: latest

Test fails because tries to download assets that are not yet created.

The test code swtpm_env_setup.pm contains this workaround which now can be removed, by expressing START_AFTER_TEST referencing a cross-machine dependency
as explained in https://github.com/os-autoinst/openQA/blob/master/docs/WritingTests.asciidoc#inter-machine-dependencies

    # Since machine:RPi4 and machine:aarch64 are using different flavors,
    # and we can not add `START_AFTER_TEST` dependencies between jobs in
    # different flavors, so we need to wait create_swtpm_hdd job finished
    # here if this test is running on machine:RPi4
Actions #1

Updated by amanzini 11 months ago

  • Tags set to fail
Actions #2

Updated by pstivanin 11 months ago

  • Status changed from New to In Progress
  • Assignee set to pstivanin
Actions #3

Updated by pstivanin 11 months ago

  • Subject changed from [security] test fails in swtpm_env_setup to [security][15-SP4] test fails in swtpm_env_setup
Actions #4

Updated by pstivanin 11 months ago

  • % Done changed from 0 to 20

the issue is that START_AFTER_TEST is not picked up. looking into why this is happening

Actions #5

Updated by pstivanin 11 months ago

  • % Done changed from 20 to 70
Actions #6

Updated by pstivanin 11 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 70 to 100
Actions

Also available in: Atom PDF