Project

General

Profile

Actions
Copy link

action #104109

closed

[timebox:8h] verify_cloned_profile fails with timeout for cat /root/autoinst.xml

Added by JRivrain over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
Current
Start date:
2021-12-16
Due date:
% Done:

0%

Estimated time:

Description

Observation

The test fails tryng to do a simple "cat /root/autoinst.xml." We could try to find out why it fails. It can be a pretty big file, I tried it in a random VM with 3 cores, it took 0.4 seconds, so if the xml is really big and/or the VM very slow it could be necessary to specify some timeout.

openQA test in scenario sle-15-SP4-Online-x86_64-autoyast_iscsi_ibft@64bit fails in
verify_cloned_profile

Test suite description

AutoYaST ibft installation on iSCSI disk. iSCSI configuration is validated in the installed system, as well as cloned profile is verified to check relevant sections.

Reproducible

Fails since (at least) Build 43.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by JRivrain over 2 years ago

  • Project changed from openQA Tests to qe-yam
  • Subject changed from test fails in verify_cloned_profile to test fails in verify_cloned_profile - timeout for cat /root/autoinst.xml
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by JERiveraMoya over 2 years ago

  • Tags set to qe-yast-refinement
  • Subject changed from test fails in verify_cloned_profile - timeout for cat /root/autoinst.xml to [timebox:8h] verify_cloned_profile fails with timeout for cat /root/autoinst.xml
  • Target version set to Current
Actions
Copy link
 #3

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: autoyast_iscsi_ibft
https://openqa.suse.de/tests/7924403

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions
Copy link
 #4

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Rejected

Once the previous test is fixed https://openqa.suse.de/tests/7950030#step/verify_cloned_profile/4, we don't see this break of the console which doesn't allow to display the file.
Let's reject it for now and reopen if fails again.

Actions
Copy link

Also available in: Atom PDF