Project

General

Profile

Actions

action #93110

closed

test fails in dhcp_no - install libyui-rest-api* when yuirest api has called

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

Status:
Closed
Priority:
High
Assignee:
Target version:
SUSE QA - SLE 15 SP3
Start date:
2021-05-25
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario opensuse-15.3-DVD-x86_64-yast2_ncurses@64bit fails in
dhcp_no

Since these params has called YUI_HTTP_PORT=$yuiport YUI_HTTP_REMOTE=1 YUI_REUSE_PORT=1 then the system must to have libyui-rest-api* do existed, otherwise throws a error as fails to load rest plugin.
Note that, libyui-rest-api version can be different per openSUSE/SLE version.

Test suite description

Maintainer: qsf-y Test for yast2 UI, ncurses only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
riafarov set TIMEOUT_SCALE to improve stability of the test.

Reproducible

Fails since (at least) Build 160.3

Expected result

Last good: 152.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by maritawerner about 3 years ago

  • Subject changed from test fails in dhcp_no - install libyui-rest-api* when yuirest api has called to [y] test fails in dhcp_no - install libyui-rest-api* when yuirest api has called
Actions #2

Updated by oorlov about 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Subject changed from [y] test fails in dhcp_no - install libyui-rest-api* when yuirest api has called to test fails in dhcp_no - install libyui-rest-api* when yuirest api has called
  • Category deleted (Bugs in existing tests)
  • Priority changed from Normal to High
  • Target version set to SLE 15 SP3
Actions #3

Updated by oorlov about 3 years ago

  • Tags set to qa-yast-to-refine
Actions #4

Updated by JERiveraMoya about 3 years ago

It is missing configuration to boot gnome-libyui image in the same way that yast2 gui scenario

Actions #5

Updated by oorlov about 3 years ago

  • Tags deleted (qa-yast-to-refine)
  • Status changed from New to Workable
Actions #6

Updated by JERiveraMoya about 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions #7

Updated by JERiveraMoya about 3 years ago

VR: Leap 15.3 | TW

Actions #8

Updated by JERiveraMoya about 3 years ago

  • Status changed from In Progress to Closed
Actions #9

Updated by okurz about 3 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: yast2_ncurses
https://openqa.opensuse.org/tests/1755978

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 label in the openQA scenario is removed
Actions #10

Updated by openqa_review about 3 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: yast2_ncurses
https://openqa.opensuse.org/tests/1755978

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 label in the openQA scenario is removed
Actions #11

Updated by openqa_review almost 3 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: yast2_ncurses
https://openqa.opensuse.org/tests/1755978

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 label in the openQA scenario is removed
Actions #12

Updated by openqa_review almost 3 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: yast2_ncurses
https://openqa.opensuse.org/tests/1755978

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 label in the openQA scenario is removed
Actions

Also available in: Atom PDF