https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-03-07T15:08:07ZopenSUSE Project Management ToolopenQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6100492023-03-07T15:08:07Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>175</i> to <i>openQA Infrastructure</i></li></ul> openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6100612023-03-07T15:21:21Zokurzokurz@suse.com
<ul></ul><p>Added ssh key of <a href="mailto:root@backup.qa.suse.de">root@backup.qa.suse.de</a> to openqaw5-xen.qa.suse.de:/root/.ssh/authorized_keys and executed</p>
<pre><code>for i in etc boot; do rsync -aHP --one-file-system openqaw5-xen.qa.suse.de:/$i/ $i/; done
ssh openqaw5-xen.qa.suse.de "rpm -qa" > rpm_list_$(date +%F).txt
</code></pre>
<p>Then we did <code>zypper migration</code> to go to SLE15-SP4 first.</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6101092023-03-07T18:29:11Zokurzokurz@suse.com
<ul></ul><p>system is on SLE15-SP4 without a reboot so far. I would prefer if we would have a working SoL before a reboot but if I don't get any useful hint I will trigger a reboot regardless</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6101692023-03-08T04:11:25Zopenqa_reviewopenqa-review@suse.de
<ul><li><strong>Due date</strong> set to <i>2023-03-22</i></li></ul><p>Setting due date based on mean cycle time of SUSE QE Tools</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6109072023-03-08T19:25:44Zokurzokurz@suse.com
<ul></ul><p>I then copied over /etc/zypp/repos.d/ files from a clean Leap 15.4 to the machine and called</p>
<pre><code>zypper --releasever=15.4 ref && zypper --releasever=15.4 dup --details --allow-vendor-change --allow-downgrade --replacefiles --auto-agree-with-licenses --download-in-advance && zypper -n in --force openSUSE-release
</code></pre>
<p>and the result looked good. Then I added the machine to salt following<br>
<a href="https://gitlab.suse.de/openqa/salt-states-openqa/#how-to-use" class="external">https://gitlab.suse.de/openqa/salt-states-openqa/#how-to-use</a><br>
started the salt-minion, accepted the salt key on osd and applied a state test-wise with</p>
<pre><code>sudo salt --no-color --state-output=changes 'openqaw5-xen.qa.suse.de' state.apply test=True
</code></pre>
<p>and then for real.</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6109282023-03-08T19:58:41Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>Some minutes later <a href="https://monitor.qa.suse.de/d/GDopenqaw5-xen/dashboard-for-openqaw5-xen?orgId=1&refresh=1m" class="external">https://monitor.qa.suse.de/d/GDopenqaw5-xen/dashboard-for-openqaw5-xen?orgId=1&refresh=1m</a> nicely shows up-to-date data.</p>
<p><code>systemctl --failed</code> shows suseconnect-keepalive.timer so I uninstalled suseconnect-ng</p>
<p>Then to test boot I called</p>
<pre><code>qemu-system-x86_64 -m 4096 -snapshot /dev/sda -vnc :99
</code></pre>
<p>and connected with <code>vncviewer -Shared openqaw5-xen.qa.suse.de:5999 and saw an error that grub wuoldn't be able to find a file on btrfs filesystem. I aborted the VM, called</code>update-bootloader && sync` and another try looked good. The system booted into the Xen kernel which eventually showed an error that there is not enough memory to reserve for Dom0. So I did</p>
<pre><code>systemctl stop libvirtd
for i in {1..8}; do xl destroy openQA-SUT-$i; done
</code></pre>
<p>but that did not give the host more than 3GB reported memory. So I finally decided to reboot.</p>
<p>Machine came up just fine</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6110392023-03-09T08:13:30Zokurzokurz@suse.com
<ul></ul><p>Due to problems reported in <a href="https://suse.slack.com/archives/C02CANHLANP/p1678348127516429?thread_ts=1678213854.333779&cid=C02CANHLANP" class="external">https://suse.slack.com/archives/C02CANHLANP/p1678348127516429?thread_ts=1678213854.333779&cid=C02CANHLANP</a> I removed the machine from salt again for now and changed sshd config back to allow root login with password. We should find a proper solution for tests or extend salt to cover that.</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6113932023-03-09T11:44:43Zmkittlermarius.kittler@suse.com
<ul></ul><p><code>suseconnect-keepalive.timer</code> was failing (triggering the systemd services alert). It looks like the problem was already resolved, though.</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6117382023-03-10T07:20:47Zokurzokurz@suse.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" href="/issues/125750">action #125750</a>: In salt-states-openqa support machines requiring ssh password login for root user size:M</i> added</li></ul> openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6117442023-03-10T07:21:08Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> deleted (<del><i>2023-03-22</i></del>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Blocked</i></li></ul><p>blocking on <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: In salt-states-openqa support machines requiring ssh password login for root user size:M (Resolved)" href="https://progress.opensuse.org/issues/125750">#125750</a></p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6257152023-04-20T09:07:38Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2023-05-04</i></li><li><strong>Status</strong> changed from <i>Blocked</i> to <i>In Progress</i></li></ul><p><a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: In salt-states-openqa support machines requiring ssh password login for root user size:M (Resolved)" href="https://progress.opensuse.org/issues/125750">#125750</a> resolved, continuing.</p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6257992023-04-20T10:35:48Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> deleted (<del><i>2023-05-04</i></del>)</li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Blocked</i></li></ul><p>back to <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: In salt-states-openqa support machines requiring ssh password login for root user size:M (Resolved)" href="https://progress.opensuse.org/issues/125750">#125750</a></p>
openQA Infrastructure - action #125534: Consolidate the installation of openqaw5-xen with SUSE QE Tools maintained machines size:Mhttps://progress.opensuse.org/issues/125534?journal_id=6268732023-04-24T12:46:15Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Resolved</i></li></ul><p><a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: In salt-states-openqa support machines requiring ssh password login for root user size:M (Resolved)" href="https://progress.opensuse.org/issues/125750">#125750</a> was now properly resolved. </p>
<p>okurz wrote:</p>
<blockquote>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> openqaw5-xen shows up in monitor.qa.suse.de</li>
</ul>
</blockquote>
<p><a href="https://monitor.qa.suse.de/d/GDopenqaw5-xen/dashboard-for-openqaw5-xen?orgId=1&refresh=1m" class="external">https://monitor.qa.suse.de/d/GDopenqaw5-xen/dashboard-for-openqaw5-xen?orgId=1&refresh=1m</a></p>
<blockquote>
<ul>
<li><strong>AC2:</strong> openqaw5-xen has an updated OS</li>
</ul>
</blockquote>
<p>confirmed, Leap 15.4 with continuous patching and automatic rebooting in the Sunday morning maintenance window</p>
<blockquote>
<ul>
<li><strong>AC3:</strong> openqaw5-xen basics are administered by SUSE QE Tools</li>
</ul>
</blockquote>
<p>confirmed, in salt now</p>