https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842017-09-13T10:11:16ZopenSUSE Project Management ToolopenQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=641202017-09-13T10:11:16ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>It has to be decided yet if they should have dedicated hardware for that or they should used shared workers like the Yast team.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=651202017-09-20T21:36:22Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Infrastructure</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=651402017-09-20T21:40:29Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>openQA-workers for systemd department</i> to <i>[sle][functional]openQA-workers for systemd department</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=658722017-09-27T12:41:40Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[sle][functional]openQA-workers for systemd department</i> to <i>[tools][systemd]openQA-workers for systemd department</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=812752018-01-02T10:10:57Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Milestone 14</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=847422018-01-20T12:45:09Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2018-03-13</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=924972018-02-20T21:26:16Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-03-13</i> to <i>2018-04-24</i></li><li><strong>Target version</strong> changed from <i>Milestone 14</i> to <i>Milestone 15</i></li></ul><p>M14 is too full. Better we focus more on fixing.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1099122018-04-05T12:41:41Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Subject</strong> changed from <i>[tools][systemd]openQA-workers for systemd department</i> to <i>[tools][systemd][u] openQA-workers for systemd department</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1113552018-04-10T13:23:43Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[tools][systemd][u] openQA-workers for systemd department</i> to <i>[tools][functional][systemd][u] openQA-workers for systemd department</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1113912018-04-10T13:52:29Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-04-24</i> to <i>2018-05-08</i></li></ul><p>Because we are not moving anywhere with these tickets let's work on the webui server as a prerequisite in <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: [tools][functional][u][systemd][medium]openQA-webui for systemd virtual team (Resolved)" href="https://progress.opensuse.org/issues/25246">#25246</a> first.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1113972018-04-10T13:53:11Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 15</i> to <i>Milestone 16</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1135062018-04-18T08:53:54Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed child" href="/issues/25246">action #25246</a>: [tools][functional][u][systemd][medium]openQA-webui for systemd virtual team</i> added</li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1135122018-04-18T08:54:35Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/113512/diff?detail_id=113368">diff</a>)</li><li><strong>Assignee</strong> set to <i>SLindoMansilla</i></li></ul><p>To be done:</p>
<ul>
<li>Decide if we help them to set it up themselves or if we set the workers up for them</li>
<li>Try to motivate the systemd department to drive this</li>
</ul>
<p>Sergio will contact them to clarify machine resources</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1142172018-04-20T13:38:26ZSLindoMansillaslindomansilla@suse.com
<ul></ul><ul>
<li>systemd team has a webui: <a href="http://emerson.suse.de" class="external">http://emerson.suse.de</a></li>
<li>they don't have any worker machine for aarch64, ppc64le nor s390x.</li>
<li>at the moment <a href="http://emerson.suse.de" class="external">http://emerson.suse.de</a> is also used as a x86_64 worker for qemu backend, but it is a too week machine that cannot handle the webui and x86_64 workers for the team.</li>
<li>tblume has access to a s390x machine, but he needs it for debugging. Maybe we could find a way that he can use it for both, debugging and as openQA-worker-SUT.</li>
<li>tblume will take care of looking for aarch64 and ppc64le and x86_64 machines in orthos. After that, we should help them know how to configure those machines as SUT for remote workers.</li>
</ul>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1151682018-04-24T13:49:56ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/115168/diff?detail_id=115150">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> deleted (<del><i>SLindoMansilla</i></del>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul><p>At the moment tsaupe has to look for machines (aarch64, ppc64le, s390x, x86_64) for his team. We have to wait for him. This task is not yet workable.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1166132018-04-30T11:58:16Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> set to <i>tsaupe</i></li></ul><p>Hi tsaupe, as stated by SLindoMansilla in <a class="issue tracker-4 status-3 priority-3 priority-lowest closed child" title="action: [tools][functional][systemd][u] openQA-workers for systemd department (Resolved)" href="https://progress.opensuse.org/issues/25248#note-15">#25248#note-15</a> we are waiting for you to "look for machines". This is why I will assign this ticket to you assuming you will respond back when you either have found machine ressources useable for openQA workers or a question how we can help you.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1179542018-05-07T07:52:13Ztsaupethomas.blume@suse.com
<ul></ul><p>okurz wrote:</p>
<blockquote>
<p>Hi tsaupe, as stated by SLindoMansilla in <a class="issue tracker-4 status-3 priority-3 priority-lowest closed child" title="action: [tools][functional][systemd][u] openQA-workers for systemd department (Resolved)" href="https://progress.opensuse.org/issues/25248#note-15">#25248#note-15</a> we are waiting for you to "look for machines". This is why I will assign this ticket to you assuming you will respond back when you either have found machine ressources useable for openQA workers or a question how we can help you.</p>
</blockquote>
<p>I've got machines for x86_64 and ppc64le.<br>
I've installed SLES12SP3 but need to postpone further processing, because I'm currently vacation backup for systemd and have to process high priority bugs.<br>
I expect to continue processing next week.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1183122018-05-08T08:59:54Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-05-08</i> to <i>2018-06-05</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1233522018-06-05T08:15:13Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-06-05</i> to <i>2018-06-19</i></li><li><strong>Target version</strong> changed from <i>Milestone 16</i> to <i>Milestone 17</i></li></ul><p>@Thomas any update? :) <br>
Need help with something?</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1235502018-06-05T09:28:16Ztsaupethomas.blume@suse.com
<ul></ul><p>mgriessmeier wrote:</p>
<blockquote>
<p>@Thomas any update? :) <br>
Need help with something?</p>
</blockquote>
<p>Actually, the machines are up and running.<br>
We could start the worker setup.<br>
I'm just very busy with bugs and need a timeslot.<br>
Also I'm currently using the ppc machine for reproducing bug 1092896.<br>
Is it still possible to use the machine as reproducer after the openqa worker setup?</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1240122018-06-05T14:28:01ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>Hi Thomas,</p>
<p>Well, as long as there is no re-installation of the OS, it is possible.<br>
Can you describe what you do to reproduce bugs there?</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1243032018-06-06T05:58:51Ztsaupethomas.blume@suse.com
<ul></ul><p>SLindoMansilla wrote:</p>
<blockquote>
<p>Hi Thomas,</p>
<p>Well, as long as there is no re-installation of the OS, it is possible.<br>
Can you describe what you do to reproduce bugs there?</p>
</blockquote>
<p>I'm downloading the test image from the test run that was reported to fail and run it in virt-manager on my machine.<br>
I can then install the testsuite and start the test manually inside this vm.<br>
That turned out to be very convenient for debugging.</p>
<p>Also, when systemd is updated to a newer version, there are usually more tests added.<br>
That means I need to adapt the testsuite package and thus need one machine for each architecture where I can start it.<br>
I'm currently trying to get another machine for aarch64, so that I can adapt the testsuite (see latest entry in bug 1092896).</p>
<p>However, I don't need those machines permanently for development, so I guess the openQA setup could co-exist with my development system there.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1243542018-06-06T07:34:55Zokurzokurz@suse.com
<ul></ul><p>Yes, you can definitely run VMs using libvirtd+virt-manager in parallel to openQA workers on that machine.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1252812018-06-07T10:42:00Ztsaupethomas.blume@suse.com
<ul></ul><p>okurz wrote:</p>
<blockquote>
<p>Yes, you can definitely run VMs using libvirtd+virt-manager in parallel to openQA workers on that machine.</p>
</blockquote>
<p>Ok, so let's make an appointment for the openQA setup on my ppc64le, and x86_64 VM.<br>
If it suits you, next week Monday or Tuesday would be fine.<br>
For the time, I don't have preferences, just pick what is convenient for you.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1252992018-06-07T11:02:40ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>Monday at 13:30?</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1253082018-06-07T11:22:54Ztsaupethomas.blume@suse.com
<ul></ul><p>SLindoMansilla wrote:</p>
<blockquote>
<p>Monday at 13:30?</p>
</blockquote>
<p>Ok, fine for me.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1266822018-06-12T12:25:45Ztsaupethomas.blume@suse.com
<ul></ul><p>Status update:</p>
<p>remote workers configured for x86_64 and ppc64le</p>
<p>I'm unable to get a permanent machine reservation on an aarch64 host.<br>
There is also a technical problem, aarch64 doesn't support virtualization nesting.<br>
That makes the current testsuite setup for the extended tests unusable.<br>
Looking for a solution.</p>
<p>For s390x, I'm still looking for a machine.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1291752018-06-15T18:54:03Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 17</i> to <i>Milestone 17</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1306662018-06-19T08:11:19Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> changed from <i>2018-06-19</i> to <i>2018-07-03</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1306692018-06-19T08:11:38Zmgriessmeiermgriessmeier@suse.com
<ul></ul><p>tsaupe wrote:</p>
<blockquote>
<p>For s390x, I'm still looking for a machine.</p>
</blockquote>
<p>Can I support you here?</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1307142018-06-19T08:24:08Ztsaupethomas.blume@suse.com
<ul></ul><p>mgriessmeier wrote:</p>
<blockquote>
<p>tsaupe wrote:</p>
<blockquote>
<p>For s390x, I'm still looking for a machine.</p>
</blockquote>
<p>Can I support you here?</p>
</blockquote>
<p>Sure, I'd be happy if you could give me a VM.<br>
All orthos machines have by far too few resources for the tests.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1307172018-06-19T08:25:14ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/36754">action #36754</a>: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation</i> added</li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1312422018-06-20T09:13:53Zriafarov
<ul></ul><p>Clarify if can solve aarch64 workers issue first.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1317242018-06-21T15:04:35ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>s390x worker already working.</p>
<p>Only aarch64 missing. Need to research how to enable kvm virtualization for aarch64 on SLE12-SP3 or SLE15.</p>
<p>SR about packages needed by os-autoinst when using svirt backend (s390x, xen): <a href="https://build.opensuse.org/request/show/618317" class="external">https://build.opensuse.org/request/show/618317</a></p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1341952018-07-03T08:35:46Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Due date</strong> deleted (<del><i>2018-07-03</i></del>)</li><li><strong>Target version</strong> changed from <i>Milestone 17</i> to <i>Milestone 21+</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1696972018-11-28T17:10:17ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/36754">action #36754</a>: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation</i>)</li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1697062018-11-28T17:10:27ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/36754">action #36754</a>: [qe-core][functional][systemd][medium] test fails in systemd_testsuite - needs further investigation</i> added</li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1697092018-11-28T17:12:40ZSLindoMansillaslindomansilla@suse.com
<ul></ul><p>Hi Thomas,</p>
<p>if I remember properly, you already got aarch64, ppc64le, s390x and x86_64 workers for your openQA instance. If so, could you resolve this ticket?</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1734862018-12-12T16:52:28Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 21+</i> to <i>Milestone 21</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1746022018-12-18T10:09:55ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Workable</i></li></ul><p>systemd team is still missing an aarch64 worker</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1746052018-12-18T10:20:13Ztsaupethomas.blume@suse.com
<ul></ul><p>SLindoMansilla wrote:</p>
<blockquote>
<p>systemd team is still missing an aarch64 worker</p>
</blockquote>
<p>It seems we have insufficient machines on aarch64 to get a fixed worker slaves.<br>
Since all the other slaves are set up, I can live with that.<br>
If in need, I will try to use an orthos machine instead.</p>
<p>I'm closing the ticket therewith.</p>
openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1746202018-12-18T10:27:24ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> openQA Tests - action #25248: [tools][functional][systemd][u] openQA-workers for systemd departmenthttps://progress.opensuse.org/issues/25248?journal_id=1746232018-12-18T10:27:37ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul>