Project

General

Profile

Actions

action #34759

closed

[qe-core][sle][functional][medium] Add debug output in reconnect_s390 also for z/VM when bootup is stuck (not reaching login prompt but ssh is reachable)

Added by mgriessmeier over 6 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Enhancement to existing tests
Target version:
-
Start date:
2018-04-10
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:
medium

Description

User Story

Followup on this PR. Apparently there are some flaws, e.g. Started OpenSSH Daemon not shown reliably
the PR only covers KVM, should be extended to cover z/VM as well

Acceptance Criteria

AC1: bsc#1083646 workaround is handled properly on z/VM testcases
AC2: SSH based debug output in case of 'login not found' is handled accordingly


Related issues 2 (0 open2 closed)

Related to openQA Tests - action #44588: [functional][u][svirt] test fails in bootloader_svirt - test started typing before actually logging inResolvedmgriessmeier2018-11-30

Actions
Copied from openQA Tests - action #34609: [sle][functional][u][medium] Improve Implementation of workaround for bsc#1083646 and debug output in reconnect_s390 on S390-KVMRejectedmgriessmeier2018-04-102018-04-24

Actions
Actions #1

Updated by mgriessmeier over 6 years ago

  • Copied from action #34609: [sle][functional][u][medium] Improve Implementation of workaround for bsc#1083646 and debug output in reconnect_s390 on S390-KVM added
Actions #2

Updated by okurz over 6 years ago

  • Subject changed from [sle][functional][u][medium] Applyworkaround for bsc#1083646 and debug output in reconnect_s390 also for z/VM to [sle][functional][u][medium] Apply workaround for bsc#1083646 and debug output in reconnect_s390 also for z/VM
Actions #3

Updated by mgriessmeier over 6 years ago

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

Bug is fixed, debug output is already decent here.
Still we should check if it can be improved, but priority is low

Actions #4

Updated by mgriessmeier over 6 years ago

  • Priority changed from High to Normal
Actions #5

Updated by okurz over 6 years ago

  • Subject changed from [sle][functional][u][medium] Apply workaround for bsc#1083646 and debug output in reconnect_s390 also for z/VM to [sle][functional][u][medium] Add debug output in reconnect_s390 also for z/VM when bootup is stuck (not reaching login prompt but ssh is reachable)
  • Priority changed from Normal to Low

as you stated, prio is low :)

We can always bump up prio if we again run into an issue similar to bsc#1083646

Actions #6

Updated by okurz over 6 years ago

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

Updated by okurz about 6 years ago

  • Target version changed from Milestone 18 to future
Actions #8

Updated by okurz almost 6 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: ext4
https://openqa.suse.de/tests/2320006

Actions #9

Updated by okurz almost 6 years ago

  • Related to action #44588: [functional][u][svirt] test fails in bootloader_svirt - test started typing before actually logging in added
Actions #10

Updated by SLindoMansilla about 5 years ago

  • Target version changed from future to Milestone 27
  • Estimated time set to 42.00 h
Actions #11

Updated by mgriessmeier about 5 years ago

  • Priority changed from Low to Normal
  • Target version changed from Milestone 27 to Milestone 28
Actions #12

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 28 to Milestone 31
Actions #13

Updated by tjyrinki_suse about 4 years ago

  • Subject changed from [sle][functional][u][medium] Add debug output in reconnect_s390 also for z/VM when bootup is stuck (not reaching login prompt but ssh is reachable) to [qe-core][sle][functional][medium] Add debug output in reconnect_s390 also for z/VM when bootup is stuck (not reaching login prompt but ssh is reachable)
Actions #14

Updated by okurz about 3 years ago

I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives

First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Actions #15

Updated by slo-gin about 2 years ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #16

Updated by slo-gin 8 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #17

Updated by mgrifalconi 7 months ago

  • Tags set to qecore-cleanup
  • Status changed from Workable to Rejected

6 years old ticket with no updates since years. Please create new one or reopen if you feel is still necessary.

Actions #18

Updated by okurz 7 months ago

  • Status changed from Rejected to Workable
  • Priority changed from Normal to Low
  • Target version deleted (Milestone 31)

Yes, I feel this is still necessary. The initial boot phase for s390x openQA jobs is still far from obvious what's going on

Actions #19

Updated by szarate 7 months ago ยท Edited

  • Status changed from Workable to Rejected
  • Assignee set to szarate

#28630 has better chances to be worked on. That aside zVM does not have problems that I know of.

Actions

Also available in: Atom PDF