https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842017-02-28T07:02:17ZopenSUSE Project Management ToolopenQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=420922017-02-28T07:02:17Zokurzokurz@suse.com
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: qam-minimal-full<br>
<a href="http://openqa.suse.de/tests/786614" class="external">http://openqa.suse.de/tests/786614</a></p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=421022017-02-28T07:12:51Zokurzokurz@suse.com
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: qam-minimal-full<br>
<a href="http://openqa.suse.de/tests/786614" class="external">http://openqa.suse.de/tests/786614</a></p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=436662017-03-13T18:20:13Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>test fails in shutdown</i> to <i>[qam][opensuse] test fails in shutdown</i></li></ul> openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=439402017-03-15T09:30:10Zatighineanualexei.tighineanu@suse.com
<ul></ul><p>related <a href="https://openqa.suse.de/tests/805859" class="external">https://openqa.suse.de/tests/805859</a><br>
related <a href="https://openqa.suse.de/tests/797265" class="external">https://openqa.suse.de/tests/797265</a></p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=451162017-03-27T10:01:16Zpgeorgiadispgeorgiadis@suse.com
<ul></ul><p>related: <a href="https://openqa.suse.de/tests/836019" class="external">https://openqa.suse.de/tests/836019</a><br>
related: <a href="https://openqa.suse.de/tests/838580" class="external">https://openqa.suse.de/tests/838580</a><br>
related: <a href="https://openqa.suse.de/tests/838582" class="external">https://openqa.suse.de/tests/838582</a><br>
related: <a href="https://openqa.suse.de/tests/845014#step/shutdown/19" class="external">https://openqa.suse.de/tests/845014#step/shutdown/19</a></p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=475822017-04-14T06:01:50Zokurzokurz@suse.com
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: qam-minimal-full<br>
<a href="https://openqa.suse.de/tests/874792" class="external">https://openqa.suse.de/tests/874792</a></p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=486462017-04-27T12:07:24Zvpelcakvpelcak@suse.com
<ul></ul><a name="Test-died-console-sut-is-not-activated-at-varlibopenqacacheopenqasusedetestssletestsx11shutdownpm-line-131"></a>
<h1 >Test died: console sut is not activated. at /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/x11/shutdown.pm line 131.<a href="#Test-died-console-sut-is-not-activated-at-varlibopenqacacheopenqasusedetestssletestsx11shutdownpm-line-131" class="wiki-anchor">¶</a></h1>
<p>It seems that just action click was not performed.</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=486662017-04-27T14:35:02Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qam][opensuse] test fails in shutdown</i> to <i>[qam][opensuse] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screen</i></li><li><strong>Category</strong> changed from <i>Bugs in existing tests</i> to <i>Enhancement to existing tests</i></li></ul><p>the last message is actually about <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: VNC reconnect feature needed for xen/svirt and stalled VNC connections (Resolved)" href="https://progress.opensuse.org/issues/17658">#17658</a> so a different one. See what happens when people open tickets which are way too generic in their subject ;-)</p>
<p>I updated ticket accordingly to the original description</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=486682017-04-27T14:35:11Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed parent" href="/issues/14068">action #14068</a>: [tools] Gather more system information and logs in case of boot/reboot times out</i> added</li></ul> openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=648382017-09-19T16:45:49Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qam][opensuse] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screen</i> to <i>[qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screen</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p><a href="https://freedesktop.org/wiki/Software/systemd/Debugging/" class="external">https://freedesktop.org/wiki/Software/systemd/Debugging/</a> should be a helpful reference as well.</p>
<p><a href="https://bugzilla.suse.com/show_bug.cgi?id=1055462" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1055462</a> was a bug I created recently for a SLE15 failure which I subsequently closed with WORKSFORME because the problem of not shutting down in time was a sporadic one and I could not provide useful debugging information. Thinking about better post fail hook handling here should be helpful.</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=649722017-09-20T20:20:59Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Milestone 11</i></li></ul> openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=660402017-09-29T06:23:55Zokurzokurz@suse.com
<ul></ul><p>Latest example of "openQA-in-openQA" test scenario failing: <a href="https://openqa.opensuse.org/tests/494083#step/shutdown/1" class="external">https://openqa.opensuse.org/tests/494083#step/shutdown/1</a> The test states that the system does not shutdown in time but without any more helpful information. That's very hard to debug as in: No one will care unless we improve the debugging output in the test code.</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=662422017-10-01T06:00:58Zokurzokurz@suse.com
<ul></ul><p><a href="https://openqa.opensuse.org/tests/484400#step/shutdown/13" class="external">https://openqa.opensuse.org/tests/484400#step/shutdown/13</a></p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=674142017-10-12T19:14:57Zsebchladsebastian.chlad@suse.com
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a>: as you have added this to QA SLE Functional scrum team 19.09 - is this important for QA SLE: SLE15 testing?<br>
I do not question this is useful, especially for openSuse. I would like to check however that this is indeed QA SLE Functional scope.</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=676542017-10-15T08:30:21Zokurzokurz@suse.com
<ul></ul><p>Did you read <a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" title="action: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. p... (Resolved)" href="https://progress.opensuse.org/issues/16520#note-10">#16520#note-10</a> ? The answer for SLE is there, it's "yes".</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=690722017-10-24T14:38:06Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2017-11-08</i></li></ul> openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=697942017-10-30T10:18:21Znicksingernsinger@suse.com
<ul></ul><p>Unfortunately many of the posted links are already archived and cannot be viewed anymore. But from what I've seen we have x11/shutdown and shutdown/shutdown. x11/shutdown already contains the improved post_fail_hook mentioned by <a class="user active user-mention" href="https://progress.opensuse.org/users/609">@dimstar</a> - see: <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/x11/shutdown.pm#L40" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/x11/shutdown.pm#L40</a></p>
<p>From the name of the test ("x86_64-gnome-image@64bit") i assume it should make use of x11/shutdown, not shutdown/shutdown. Same goes for the openQA-in-openQA test. However - I'll try to uniform this to avoid duplicated code.</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=699192017-11-01T09:55:05ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>I found this case: <a href="https://openqa.opensuse.org/tests/519991#step/shutdown/4" class="external">https://openqa.opensuse.org/tests/519991#step/shutdown/4</a> when it will never press 'esc' because <code>$self->{await_shutdown}</code> is still 0 and function <code>power_action</code> is failing internally on <code>assert_shutdown</code>. Make sense to change in the post_fail_hook to <code>send_key('esc') unless $self->{await_shutdown};</code> ?</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=702192017-11-03T10:07:15Znicksingernsinger@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>nicksinger</i></li></ul><p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3858" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3858</a> just copies over the post-fail-hook of x11/shutdown.pm into shutdown/shutdown.pm. For now this should be sufficient to see at least behind plymouth. I'll create a new subticket for the "debug shutdown" epic to merge both files into one but want to talk to <a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a> first about that idea.</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=702222017-11-03T10:16:33Znicksingernsinger@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>Merged. Lets see how this turns out in production :)</p>
openQA Tests - action #16520: [qam][opensuse][sle][functional] enhance logging and debugging in case of failed shutdown, e.g. press 'esc' on plymouth splash screenhttps://progress.opensuse.org/issues/16520?journal_id=708012017-11-07T09:53:30Znicksingernsinger@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>No fallout on OSD so hopefully it helps us more next time it fails.</p>