https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842017-10-25T08:42:48ZopenSUSE Project Management ToolopenQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=692542017-10-25T08:42:48Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2017-11-22</i></li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=692742017-10-25T09:00:06Zriafarov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/25634">action #25634</a>: [sle][functional][opensuse][sporadic]test fails in yast2_firewall because "zypper in" times out -> bump timeout</i> added</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=692802017-10-25T09:00:55Zriafarov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/26104">action #26104</a>: test fails in yast2_lang</i> added</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=711512017-11-08T09:21:09Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Milestone 14</i></li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=711782017-11-08T10:11:41Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> deleted (<del><i>2017-11-22</i></del>)</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=738642017-11-22T15:25:49Zriafarov
<ul></ul><p>Experiment with killing yast processes didn't work well with firewall yast module, as we switch to root console twice to install apache module: <a href="https://openqa.opensuse.org/tests/538463#step/yast2_firewall/5" class="external">https://openqa.opensuse.org/tests/538463#step/yast2_firewall/5</a><br>
And then it doesn't work well and times out in some runs. So it's another point to get some other solution, e.g. rolling to the last good snapshot even test module was successful (currently is missing in openQA) or using YCP here (which may not resolve issues with unreliable start). Another point to check is btrfs balancing, as it's easy to see that system performance degrades during rebalancing which results in slowly starting modules. For that we can run balancing before test execution.</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=738912017-11-22T19:09:40Zokurzokurz@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>okurz</i></li></ul><p>I wondered why the btrfs balancing hasn't been run in before. I thought we do that as well for the "create_hdd" parent job. <em>But</em> as it turns out the both schedule definition files products/{opensuse,sle}/main.pm differ in this point, sle calls console/force_cron_run, opensuse does not :( That could explain a lot. So IMHO the way to go is to make sure we call console/force_cron_run as well for opensuse but this time the correct way, DRY in main.pm</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=738972017-11-22T20:09:08Zokurzokurz@suse.com
<ul></ul><p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3935" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/3935</a></p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=742722017-11-23T13:50:58Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li></ul><p>merged. Verification on production, no new fails. <a href="https://openqa.opensuse.org/tests/539692#" class="external">https://openqa.opensuse.org/tests/539692#</a> is the first yast2_gui test run in production after force_cron_run. At least it did not fail but I guess it's too early to see any issue as resolved, especially when we still have that timeout scale on the job. So next step: Test for proper statistics, remove TIMEOUT_SCALE and such</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=840072018-01-17T15:23:23Zriafarov
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>New</i></li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=917922018-02-18T21:56:12Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[opensuse][sle][functional] yast2 gui modules fail to start in the defined time frame</i> to <i>[opensuse][sle][functional][yast][hard] yast2 gui modules fail to start in the defined time frame</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/91792/diff?detail_id=90010">diff</a>)</li><li><strong>Due date</strong> set to <i>2018-03-27</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li><li><strong>Target version</strong> changed from <i>Milestone 14</i> to <i>Milestone 15</i></li></ul><p>Well, I think "New" is an understatement making people believe no one ever worked on this ticket.</p>
<p>Considering the suggestion from <a class="issue tracker-4 status-6 priority-4 priority-default closed" title="action: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time frame (Rejected)" href="https://progress.opensuse.org/issues/27004#note-9">#27004#note-9</a> it should be "workable" but hard. Also added ACs.</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1007412018-03-13T13:36:37Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> deleted (<del><i>2018-03-27</i></del>)</li><li><strong>Target version</strong> changed from <i>Milestone 15</i> to <i>Milestone 17</i></li></ul><p>no capacity in M15 or M16 left</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1032672018-03-18T15:43:57Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2018-04-10</i></li><li><strong>Target version</strong> changed from <i>Milestone 17</i> to <i>Milestone 15</i></li></ul><p>Actually it seems we do have some [yast] specific capacity. Adding to S14.</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1064742018-03-28T10:47:59Zcwhcwh@suse.com
<ul><li><strong>Difficulty</strong> set to <i>hard</i></li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1065342018-03-28T11:12:03Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[opensuse][sle][functional][yast][hard] yast2 gui modules fail to start in the defined time frame</i> to <i>[opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time frame</i></li><li><strong>Due date</strong> deleted (<del><i>2018-04-10</i></del>)</li><li><strong>Target version</strong> changed from <i>Milestone 15</i> to <i>Milestone 17</i></li></ul><p>nope, we were wrong, back to previous.</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1261602018-06-10T12:24:16Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 17</i> to <i>Milestone 19</i></li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1284762018-06-15T18:49:54Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 19</i> to <i>Milestone 19</i></li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1565962018-10-14T18:49:10Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/39719">coordination #39719</a>: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues</i> added</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1566022018-10-14T18:49:15Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/39719">coordination #39719</a>: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues</i>)</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1566112018-10-14T18:49:23Zokurzokurz@suse.com
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/39719">coordination #39719</a>: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues</i> added</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=1566142018-10-14T18:49:31Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Blocked</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li><li><strong>Target version</strong> changed from <i>Milestone 19</i> to <i>future</i></li></ul><p>Well, on o3 we still run yast2_gui with <code>TIMEOUT_SCALE=5</code> and yast2_ncurses with <code>TIMEOUT_SCALE=3</code> so this issue is still valid. By now we have improved the <code>force_scheduled_tasks</code> module so btrfs maintenance tasks are not triggered anymore in the background. However, other processes, e.g. zypper, can still trigger IO heavy tasks, e.g. handling snapper snapshots which might have bad effect. We try to detect the "known bugs" handling this issue better but are not there yet easily turn a job into a soft-fail based on detecting a "known issue". So IMHO we should work on <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="coordination: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tr... (Resolved)" href="https://progress.opensuse.org/issues/39719">#39719</a> first before going further on with this ticket.</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=2141122019-05-22T10:18:53Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> changed from <i>okurz</i> to <i>riafarov</i></li></ul><p>Move to new QSF-y PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-y. Feel free to reassign to me or someone else in this case. Thanks.</p>
openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=2148022019-05-23T08:10:54Zriafarov
<ul><li><strong>Blocked by</strong> deleted (<i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/39719">coordination #39719</a>: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues</i>)</li></ul> openQA Tests - action #27004: [opensuse][sle][functional][yast][y][hard] yast2 gui modules fail to start in the defined time framehttps://progress.opensuse.org/issues/27004?journal_id=2148052019-05-23T08:11:46Zriafarov
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Rejected</i></li></ul><p>I guess it's time to reject this one, as we have provided multiple mitigations and progress in changing way how we test yast modules too.</p>