https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-02-16T20:05:38ZopenSUSE Project Management ToolopenQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=916452018-02-16T20:05:38ZStefanBruensstefan.bruens@rwth-aachen.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/25554">action #25554</a>: [functional][bsc#1063638][u] soft fail in force_cron_run is too strict</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=937512018-02-22T21:57:14Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>force_cron_run does not actually run any crons (occasionally)</i> to <i>[functional]force_cron_run does not actually run any crons (occasionally)</i></li><li><strong>Target version</strong> set to <i>Milestone 16</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1032912018-03-18T15:59:26Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[functional]force_cron_run does not actually run any crons (occasionally)</i> to <i>[functional][u]force_cron_run does not actually run any crons (occasionally)</i></li><li><strong>Due date</strong> set to <i>2018-05-08</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1135452018-04-18T09:09:36Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/34210">action #34210</a>: [functional][u][medium]updates_packagekit_gpk restarts the updater several times</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1135512018-04-18T09:09:50Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed behind-schedule" href="/issues/34210">action #34210</a>: [functional][u][medium]updates_packagekit_gpk restarts the updater several times</i>)</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1135662018-04-18T09:13:47Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Subject</strong> changed from <i>[functional][u]force_cron_run does not actually run any crons (occasionally)</i> to <i>[functional][u][medium] force_cron_run does not actually run any crons (occasionally)</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1151832018-04-24T13:59:05Zcwhcwh@suse.com
<ul><li><strong>Difficulty</strong> set to <i>medium</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1160912018-04-26T13:37:50Zzluo
<ul><li><strong>Assignee</strong> set to <i>zluo</i></li></ul><p>will check this problem</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1164122018-04-27T12:43:23Zzluo
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul><p>checking at first since it is an occasional issue:</p>
<p><a href="https://openqa.opensuse.org/tests/664936" class="external">https://openqa.opensuse.org/tests/664936</a></p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1164312018-04-27T13:32:49Zzluo
<ul></ul><p>looks good:</p>
<p><a href="https://openqa.opensuse.org/tests/664937#step/force_cron_run/" class="external">https://openqa.opensuse.org/tests/664937#step/force_cron_run/</a></p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1174982018-05-03T07:30:38Zzluo
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>checked tests for 2 months ago and recent test run don't show up any issue with crons on o3.</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1176162018-05-03T11:31:39ZStefanBruensstefan.bruens@rwth-aachen.de
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Workable</i></li></ul><p>Have you even read the original issue description?</p>
<p>Both test runs you linked to shows no sign of any started cron jobs. If the jobs were started, there would be a line stating "Running cronjob scripts"</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1182342018-05-08T08:16:02Zzluo
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1182702018-05-08T08:42:05Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-05-08</i> to <i>2018-05-22</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1200732018-05-17T07:24:37Zzluo
<ul></ul><p>increase timeout to 120: </p>
<p>sub run {<br>
select_console 'root-console';<br>
# show dmesg output in console during cron run<br>
assert_script_run "dmesg -n 7";<br>
# Make sure there's no load before we trigger one via cron.<br>
settle_load;<br>
my $before = time;<br>
assert_script_run "bash -x /usr/lib/cron/run-crons", 1000;<br>
record_soft_failure 'bsc#1063638 - review I/O scheduling parameters of btrfsmaintenance' if (time - $before) > 120 && get_var('SOFTFAIL_BSC1063638');<br>
sleep 3; # some head room for the load average to rise<br>
settle_load;<br>
# return dmesg output to normal<br>
assert_script_run "dmesg -n 1";<br>
}</p>
<p>got expected results (6 times):</p>
<p><a href="http://e13.suse.de/tests/2448#step/force_cron_run/6" class="external">http://e13.suse.de/tests/2448#step/force_cron_run/6</a></p>
<p>More test runs triggered now.</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1201902018-05-17T15:35:48Zzluo
<ul></ul><p>checked cron job rules:</p>
<pre><code>## Type: string
## Default: ""
#
# At which time cron.daily should start. Default is 15 minutes after booting
# the system. Example setting would be "14:00".
# Due to the fact that cron script runs only every 15 minutes,
# it will only run on xx:00, xx:15, xx:30, xx:45, not at the accurate time
# you set.
DAILY_TIME=""
## Type: integer
## Default: 5
#
# Maximum days not running when using a fixed time set in DAILY_TIME.
# 0 to skip this. This is for users who will power off their system.
#
# There is a fixed max. of 14 days set, if you want to override this
# change MAX_NOT_RUN_FORCE in /usr/lib/cron/run-crons
MAX_NOT_RUN="5"
</code></pre>
<p>--</p>
<p>this is the problem I'm afraid...</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1201962018-05-17T16:32:13ZStefanBruensstefan.bruens@rwth-aachen.de
<ul></ul><p>There is another aspect here:<br>
The check was added, AFAIK, to "flush" any btrfs maintenance jobs, to avoid these influence any later running jobs.</p>
<p>Now, the btrfs cron jobs have been migrated to systemd timers:</p>
<pre><code>$> systemctl list-timers
NEXT LEFT LAST PASSED UNIT ACTIVATES
Thu 2018-05-17 19:00:00 CEST 59min left Thu 2018-05-17 18:00:03 CEST 16s ago snapper-timeline.timer snapper-timeline.service
Fri 2018-05-18 00:00:00 CEST 5h 59min left Thu 2018-05-17 00:00:05 CEST 18h ago logrotate.timer logrotate.service
Fri 2018-05-18 00:05:01 CEST 6h left Thu 2018-05-17 01:59:50 CEST 16h ago backup-sysconfig.timer backup-sysconfig.service
Fri 2018-05-18 00:10:57 CEST 6h left Thu 2018-05-17 00:20:53 CEST 17h ago backup-rpmdb.timer backup-rpmdb.service
Fri 2018-05-18 01:32:24 CEST 7h left Thu 2018-05-17 01:11:32 CEST 16h ago check-battery.timer check-battery.service
Fri 2018-05-18 10:15:22 CEST 16h left Thu 2018-05-17 10:15:22 CEST 7h ago snapper-cleanup.timer snapper-cleanup.service
Fri 2018-05-18 10:20:22 CEST 16h left Thu 2018-05-17 10:20:22 CEST 7h ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Mon 2018-05-21 00:00:00 CEST 3 days left Mon 2018-05-14 00:00:08 CEST 3 days ago btrfs-balance.timer btrfs-balance.service
Mon 2018-05-21 00:00:00 CEST 3 days left Mon 2018-05-14 00:00:08 CEST 3 days ago btrfs-trim.timer btrfs-trim.service
Mon 2018-05-21 00:00:00 CEST 3 days left Mon 2018-05-14 00:00:08 CEST 3 days ago fstrim.timer fstrim.service
Fri 2018-06-01 00:00:00 CEST 2 weeks 0 days left Tue 2018-05-01 00:00:08 CEST 2 weeks 2 days ago btrfs-scrub.timer btrfs-scrub.service
</code></pre>
<p>It should be comparatively easy to check for any soon-expiring timers (LEFT column), and trigger the the corresponding services immediately. Hopefully, retriggering the services short time after will be cheap.</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1203762018-05-18T08:23:38Zzluo
<ul></ul><p>I run "bash -x /usr/lib/cron/run-crons" on just rebooted sles 15. No cron job got executed. </p>
<p>To me this command can work (it still depends on system timers.), but it has not to work as we assumed for executing cron jobs on a running system with very short online duration.</p>
<p>I'll ask coolo about this. We might think about to run each cron jobs separately. But at first I want to make sure about:</p>
<pre><code>Summary: Avoid suprises later and run the cron jobs explicitly
</code></pre> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1206462018-05-18T13:29:57Zzluo
<ul></ul><p><a href="http://e13.suse.de/tests/2518#step/force_cron_run/6" class="external">http://e13.suse.de/tests/2518#step/force_cron_run/6</a></p>
<pre><code>my $run_daily_cronjobs = 'for file in /etc/cron.daily/*; do echo execute daily cron jobs: $file; $file; done';
assert_script_run "$run_daily_cronjobs", 1000;
</code></pre> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1206492018-05-18T13:37:24Zzluo
<ul></ul><p>PR:</p>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5097" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5097</a></p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1206552018-05-18T13:58:53ZStefanBruensstefan.bruens@rwth-aachen.de
<ul></ul><p>and once a week and once a months QA jobs still fail, as the weekly/monthly maintenance jobs suddenly run ...</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1209342018-05-22T08:58:58Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-05-22</i> to <i>2018-06-05</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1209762018-05-22T10:00:04Zzluo
<ul></ul><p>updated:</p>
<p>find /etc/cron.{hourly,daily,weekly,monthly} -type f -executable -exec echo run cron job: {} \; -exec {} \;</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1214522018-05-23T11:42:34Zzluo
<ul></ul><p>info:<br>
customers need to provide their own scripts for weekly, monthly, we don't provide packages for them, for hourly we have acronie-anacron which needs to be installed extra. systemd timers will replace cron job anyway. We can now check systemctl list-timers for details. but the question what should we do at moment.</p>
<p>coolo suggests to keep calling run-cron-jobs, but on top of it disable all systemd timers</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1214832018-05-23T13:04:06Zzluo
<ul></ul><p>PR updated now.</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1234152018-06-05T08:43:50Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-06-05</i> to <i>2018-06-19</i></li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>Target version</strong> changed from <i>Milestone 16</i> to <i>Milestone 17</i></li></ul><p>PR not merged yet, setting to feedback</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1292082018-06-15T18:54:12Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 17</i> to <i>Milestone 17</i></li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1306602018-06-19T08:11:03Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-06-19</i> to <i>2018-07-03</i></li></ul><p>discussion in PR is ongoing - moving</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1325212018-06-26T12:34:30ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/35302">coordination #35302</a>: [qe-core][opensuse][functional][epic][sporadic] Various unstable tests on o3</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1327642018-06-27T10:55:49ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/37354">action #37354</a>: [opensuse][functional][u][sporadic][medium] test fails in desktop_runner is unstable</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1327942018-06-27T11:32:11Zokurzokurz@suse.com
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/37916">action #37916</a>: [sle][functional][u] test fails in gnome_control_center - control center doesn't show up</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1328392018-06-27T12:39:33Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/36304">action #36304</a>: [opensuse][functional]sporadic][u] chromium test is unstable</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1328482018-06-27T12:54:48Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>So now more and more tasks depend on this, bumping prio</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1331032018-06-28T13:27:46Zzluo
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li></ul><p>working again on this issue</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1331302018-06-28T14:25:48Zriafarov
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed behind-schedule" href="/issues/36730">action #36730</a>: [sle][functional][y][medium] no route to the host 10.0.2.1 iscsi_client </i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1332082018-06-28T19:25:06Zokurzokurz@suse.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/37662">action #37662</a>: [opensuse][functional][u] test fails in multi_users_dm</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1334902018-06-29T08:23:46Zzluo
<ul></ul><p>verification run:<br>
<a href="http://e13.suse.de/tests/6070#step/force_cron_run" class="external">http://e13.suse.de/tests/6070#step/force_cron_run</a> (tw)<br>
<a href="http://e13.suse.de/tests/6072#step/force_cron_run" class="external">http://e13.suse.de/tests/6072#step/force_cron_run</a> (sles 12 sp4)<br>
<a href="http://e13.suse.de/tests/6077#step/force_cron_run" class="external">http://e13.suse.de/tests/6077#step/force_cron_run</a> (leap 15.0)</p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1336402018-06-29T14:19:54Zzluo
<ul></ul><p>PR updated now:</p>
<p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5097" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5097</a></p>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1339342018-07-02T13:45:26ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>PR merged, creating two tickets to handle:</p>
<ul>
<li>system_performance scenarios: <a href="https://openqa.opensuse.org/tests?match=system_performance" class="external">https://openqa.opensuse.org/tests?match=system_performance</a></li>
<li>renaming of force_cron_run</li>
</ul>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1339582018-07-02T14:07:05ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/38090">action #38090</a>: [sle][functional] Do not mask systemd timers on system_performance scenarios</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1339762018-07-02T14:16:19ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/38093">action #38093</a>: [sle][functional] Rename the module force_cron_run, it is no more only for cron jobs</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1339822018-07-02T14:18:49ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Now that the following steps to be done are properly defined on follow up tickets (following agile management), I can consider this planned ticket as resolved.</p>
<p>Next tasks (that were not planned for this sprint) are ready to be refined and planned:</p>
<ul>
<li>Do not mask systemd timers on system_performance scenarios: <a href="https://progress.opensuse.org/issues/38090" class="external">https://progress.opensuse.org/issues/38090</a></li>
<li>Rename the module force_cron_run, it is no more only for cron jobs: <a href="https://progress.opensuse.org/issues/38093" class="external">https://progress.opensuse.org/issues/38093</a></li>
</ul>
openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1340362018-07-03T06:54:31ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/18558">action #18558</a>: [sle][functional][u][hard][investigation] Snapper tests run too long</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1346422018-07-05T08:07:33Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-6 priority-high2 closed behind-schedule" href="/issues/38228">action #38228</a>: [sle12sp4][functional][u][fast] test fails in force_scheduled_tasks - need wait more time than 90s for the cron jobs finish</i> added</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1370662018-07-20T07:05:06Zriafarov
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-4 status-6 priority-4 priority-default closed behind-schedule" href="/issues/36730">action #36730</a>: [sle][functional][y][medium] no route to the host 10.0.2.1 iscsi_client </i>)</li></ul> openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)https://progress.opensuse.org/issues/31351?journal_id=1510132018-09-23T06:03:50Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/41459">action #41459</a>: [sle][functional][u] Explicit test module for btrfs snapshots cleanup performance</i> added</li></ul>