Project

General

Profile

Actions

action #33619

closed

[sle][functional][sle15][y][hyperv][medium] test fails in accept_license - popup to accept licence agreement is not coming up

Added by zluo about 6 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 17
Start date:
2018-03-21
Due date:
2018-07-03
% Done:

0%

Estimated time:
Difficulty:
medium

Description

popup to accept licence agreement is not coming up, it could be a problem for send_key next.

Observation

openQA test in scenario sle-15-Installer-DVD-x86_64-textmode@svirt-hyperv-uefi fails in
accept_license

Reproducible

Fails since (at least) Build 527.1

Expected result

Last good: 522.1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #33064: [functional][u][hyperv][hard] svirt-hyperv tests loose key presses. Related to FreeRDP update?Resolvedoorlov2018-03-122018-04-24

Actions
Actions #1

Updated by okurz about 6 years ago

  • Subject changed from [sle][functional][sles 15]test fails in accept_license - popup to accept licence agreement is not coming up to [sle][functional][sle15][fast][y][yast]test fails in accept_license - popup to accept licence agreement is not coming up
  • Due date set to 2018-03-27
  • Target version set to Milestone 15
Actions #2

Updated by riafarov about 6 years ago

  • Related to action #33064: [functional][u][hyperv][hard] svirt-hyperv tests loose key presses. Related to FreeRDP update? added
Actions #3

Updated by riafarov about 6 years ago

  • Subject changed from [sle][functional][sle15][fast][y][yast]test fails in accept_license - popup to accept licence agreement is not coming up to [sle][functional][sle15][fast][y][yast] test fails in accept_license - popup to accept licence agreement is not coming up
  • Due date deleted (2018-03-27)

Doesn't appear in the latest build, but could be reproduced after restart for the same. So I guess we should proceed with 33064 first. Removing from current sprint. Feel free to re-add.

Actions #4

Updated by riafarov about 6 years ago

  • Subject changed from [sle][functional][sle15][fast][y][yast] test fails in accept_license - popup to accept licence agreement is not coming up to [sle][functional][sle15][y][yast] test fails in accept_license - popup to accept licence agreement is not coming up
Actions #5

Updated by riafarov about 6 years ago

  • Subject changed from [sle][functional][sle15][y][yast] test fails in accept_license - popup to accept licence agreement is not coming up to [sle][functional][sle15][hyperv] test fails in accept_license - popup to accept licence agreement is not coming up

Yet another issue on hyperv, missing keys issue. Need to discuss how to proceed here.

Actions #6

Updated by okurz about 6 years ago

  • Subject changed from [sle][functional][sle15][hyperv] test fails in accept_license - popup to accept licence agreement is not coming up to [sle][functional][sle15][y][hyperv][medium] test fails in accept_license - popup to accept licence agreement is not coming up
  • Due date set to 2018-05-08
  • Status changed from New to Workable

We agreed within QSF we want to have no tickets without [y] or [u] so setting it back

Actions #7

Updated by cwh almost 6 years ago

  • Difficulty set to medium
Actions #8

Updated by okurz almost 6 years ago

  • Due date deleted (2018-05-08)
  • Target version changed from Milestone 15 to Milestone 18

S16 pretty full, we have some hyperv related tickets in already, so let's do them first and revisit this one later.

Actions #9

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 18 to Milestone 18
Actions #10

Updated by okurz almost 6 years ago

  • Due date set to 2018-07-03
  • Status changed from Workable to Rejected
  • Assignee set to okurz
  • Target version changed from Milestone 18 to Milestone 17

After we have a new, more powerful and much more stable hyperv testing host I assume this ticket does not apply anymore, any new observations should be reported explicitly either by reopening or opening a new issue.

Actions

Also available in: Atom PDF