Project

General

Profile

Actions

action #80188

closed

[opensuse][s390x] Deployment failure during DASD configuration

Added by AdaLovelace over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
2020-11-23
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

A DASD should be deconfigured, which is not successfully.
Some needles before, you can find the reason with a failure during loading the driver.

openQA test in scenario opensuse-Tumbleweed-DVD-s390x-bsc1178790@s390x-zVM-vswitch-l2 fails in
bootloader_start

Test suite description

Maintainer: slindomansilla
Try to reproduce https://bugzilla.opensuse.org/show_bug.cgi?id=1178790
dasd_configure: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0150/online: Resource temporarily unavailable

Reproducible

Fails since (at least) Build 20201121 (current job)

Expected result

The DASD should be reconfigurable.

Further details

Always latest result in this scenario: latest

Actions #1

Updated by AdaLovelace over 3 years ago

  • Subject changed from Deployment failure during DASD configuration to [qe-core]Deployment failure during DASD configuration
Actions #3

Updated by AdaLovelace over 3 years ago

  • Subject changed from [qe-core]Deployment failure during DASD configuration to [qe-core][s390x]Deployment failure during DASD configuration
Actions #4

Updated by SLindoMansilla over 3 years ago

  • Subject changed from [qe-core][s390x]Deployment failure during DASD configuration to [opensuse][s390x] Deployment failure during DASD configuration

It is not reproducible in SLE (yet?). So, the ticket will not be managed as QE-Core.

Actions #5

Updated by SLindoMansilla over 3 years ago

Hi Sarah,

Do you mean that it is not a product bug? If you also consider that it is a product bug, it should be handled in https://bugzilla.opensuse.org/show_bug.cgi?id=1178790

But, I assume you created this ticket to investigate the possibility of it not being a product bug. I have labeled scenarios textmode and textmode-server with this ticket, since I expect to workaround those scenarios to not reconfigure the disks using dasd_configure. But, if there are no facts supporting that it isn't a product bug, it should be labeled with https://bugzilla.opensuse.org/show_bug.cgi?id=1178790

The link you provided states that it is a product bug, so that should be done by developers, who don't look at progress.opensuse.org. They look at Bugzilla for bugs and Jira for features. So, I am adding a comment to the bug ticket with your link.

Actions #6

Updated by okurz over 3 years ago

  • Assignee set to AdaLovelace

SLindoMansilla wrote:

It is not reproducible in SLE (yet?). So, the ticket will not be managed as QE-Core.

effectively this means that there is likely no one else than AdaLovelace herself to follow up with that then.

@AdaLovelace SLindoMansilla has provided a good suggestion. If you can follow with this then please do so, otherwise I guess we need to argue with "SLindoMansilla" and "tjyrinki_suse" for the team QE Core to pick it up again :)

Actions #7

Updated by SLindoMansilla over 3 years ago

To clarify:

If product bug

  • Prio 1 for QE-Core: bugzilla ticket
  • Prio 2 for QE-Core: workaround test
  • Then, developers work on the bugzilla ticket. No progress.opensuse.org ticket.

If there is no product bug, but test/infrastructure needs adaptions

  • progress.opensuse.org ticket
  • does it affect testing SLE?
    • if yes, then Prio 1 for QE-Core
    • if no, then ignored by QE-Core
Actions #8

Updated by SLindoMansilla over 3 years ago

But, I could work on those progress tickets that are ignored by QE-Core.
The reason why I didn't pick this ticket is because I don't know how to investigate further if it is not a product bug. So, I continue focusing on the bug ticket.

Sarah, if you think it is a product bug, you can reject this progress.opensuse.org ticket.

Actions #9

Updated by AdaLovelace over 3 years ago

I was not sure, whether that would be a product bug or a configuration issue. That is the reason that I have created this issue.
Correct!

Actions #10

Updated by AdaLovelace over 3 years ago

  • Status changed from New to In Progress

The discussion is following in the referenced bug report. An IBM Developer will look on it.

Actions #11

Updated by AdaLovelace over 3 years ago

This bug will be handled together with the SLE bug by IBM:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=190010

Actions #12

Updated by okurz over 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: textmode-server
https://openqa.opensuse.org/tests/1509694

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"
  3. The label in the openQA scenario is removed
Actions #13

Updated by AdaLovelace over 3 years ago

Hi Oliver,

I want to add following code to the chzdev command: https://openqa.opensuse.org/tests/1514423#step/bootloader_s390/64

#Data for DASD bug
@dirs = < /proc/[0-9]* >;
assert_script_run("open (OUTPUT, ">", "/var/log/DASDBugInformation.log") or die "Can't open log file!";
foreach $dir (@dirs) {
$file1 = join '', $dir, '/comm';
open (FILE, '<' $file1);
print OUTPUT ;
close (FILE);
$file2 = join '', $dir, '/stack';
open (FILE, '<' $file2);
print OUTPUT ;
close (FILE);
}
close (OUTPUT) or "Couldn't close DASD log file!";

I can find the dasd_configure, but no "chzdev -d" with --no-root-update in os-autoinst-distri-opensuse. Our Developers require more information and gave me following bash code which is equal to the Perl code above (for the chzdev case where dasd_configure hangs).
for i in /proc/[0-9]*; do echo; cat $1/comm; cat $i/stack; done

Actions #14

Updated by AdaLovelace over 3 years ago

Log files are generated and forwarded.

Actions #15

Updated by AdaLovelace about 3 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF