openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-03-19T12:18:07ZopenSUSE Project Management Tool
Redmine openQA Infrastructure - action #157528 (Workable): Remove redundant ASM connections for powerPC m...https://progress.opensuse.org/issues/1575282024-03-19T12:18:07Znicksingernsinger@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Our current hypothesis is that the PPC HMC struggles with two simultaneous connections to the ASM at the same time. It causes the managed system to "flicker" in the webui and constantly abort any operation you execute. We should explore if these connection issues can be resolved by only having one, single connection between ASM<->HMC.</p>
<p>Machines where this happens:</p>
<ul>
<li>soapberry</li>
<li>blackcurrant</li>
</ul>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> <a href="https://powerhmc1.oqa.prg2.suse.org/" class="external">https://powerhmc1.oqa.prg2.suse.org/</a> shows no flickering anymore for machines going between "No connection" and "operating"</li>
<li><strong>AC2:</strong> racktables is up-to-date</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Research upstream what IBM suggests. We assume it's not foreseen that one connects more than one physical network connection to the same HMC</li>
<li>Create an infra ticket according to <a href="https://progress.opensuse.org/projects/qa/wiki/Tools#SUSE-IT-ticket-handling" class="external">https://progress.opensuse.org/projects/qa/wiki/Tools#SUSE-IT-ticket-handling</a> asking to remove the secondary, redundant network connection. At best physically remove and update racktables, not in switch config so that not somebody else some months later tries to "fix" a disabled switch port</li>
<li>Ensure that machines are still controllable over HMC after cable removal</li>
<li>Ensure that racktables is up-to-date with the remaining connection</li>
</ul>
openQA Infrastructure - action #125219 (New): Use qa-power8 for ppc tests in o3 - try the other s...https://progress.opensuse.org/issues/1252192023-03-01T10:57:42Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>The machine "power8" is currently not available for o3 meaning there is currently no ppc testing in o3 at all. Use the existing machine qa-power8 for o3 ppc testing</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC0:</strong> We know what kind of setup we need (baremetal vs. HMC managed, e.g. ask test maintainers)</li>
<li><strong>AC1:</strong> We can manage VMs on qa-power8 usable for openQA (either baremetal or HMC based)</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Wait for <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Use qa-power8 for ppc tests in o3 - try one of the suggestions size:M (Resolved)" href="https://progress.opensuse.org/issues/125216">#125216</a></li>
<li>Do the other three suggestions</li>
</ul>
<a name="Out-of-scope"></a>
<h2 >Out of scope<a href="#Out-of-scope" class="wiki-anchor">¶</a></h2>
<ul>
<li>Install openQA-worker on the machine</li>
<li>Create SUSE-IT EngInfra ticket to move the machine's ethernet interface based on racktables information to the o3 network (VLAN 662)</li>
<li>Add according networking information on o3 into /etc/dnsmasq.d/openqa.conf</li>
<li>Configure the machine OS for dhcp client mode and ensure the machine gets an address from o3 dnsmasq</li>
<li>Ensure the system is able to execute openQA tests from o3</li>
</ul>
openQA Infrastructure - action #125216 (Resolved): Use qa-power8 for ppc tests in o3 - try one of...https://progress.opensuse.org/issues/1252162023-03-01T10:56:42Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p><del>The machine "power8" is currently not available for o3 meaning there is currently no ppc testing in o3 at all.</del> Currently qa-power8-3 is the only machine providing ppc64le qemu based testing for o3 meaning that we do not have redundancy. The goal is to use the existing machine qa-power8 for o3 ppc testing as well.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> We can manage VMs on qa-power8 usable for openQA (either qemu based on a baremetal-OPAL-installation or HMC based, whatever is easier)</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Do one of the following suggestions from <a class="issue tracker-4 status-6 priority-3 priority-lowest closed child" title="action: Use qa-power8 for ppc tests in o3 - network connected? (Rejected)" href="https://progress.opensuse.org/issues/119059#note-47">#119059#note-47</a>
<ol>
<li>Physically connect keyboard+display(or serial)+storage to the machine, install Linux and enable remote IPMI</li>
<li>Connect back to HMC, install VM and try to enable remote ipmi to the bare-metal machine and then set back to OPAL and continue with bare-metal Linux installation (preferred by cdywan, sriedel, nicksinger)</li>
<li>Follow up with the discussions with IBM in bugzilla to find out what is the right way to install remote controlled bare-metal in OPAL mode (preferred by mkittler, okurz)</li>
<li>As discussed in <a class="issue tracker-4 status-6 priority-3 priority-lowest closed child" title="action: Use qa-power8 for ppc tests in o3 - network connected? (Rejected)" href="https://progress.opensuse.org/issues/119059#note-43">#119059#note-43</a> as alternative: we could continue with the HMC mode. This would likely mean setting up an HMC within the o3 network (or making HMC 3 somehow accessible).</li>
</ol></li>
</ul>
<a name="Out-of-scope"></a>
<h2 >Out of scope<a href="#Out-of-scope" class="wiki-anchor">¶</a></h2>
<ul>
<li>Install openQA-worker on the machine</li>
<li>Create SUSE-IT EngInfra ticket to move the machine's ethernet interface based on racktables information to the o3 network (VLAN 662)</li>
<li>Add according networking information on o3 into /etc/dnsmasq.d/openqa.conf</li>
<li>Configure the machine OS for dhcp client mode and ensure the machine gets an address from o3 dnsmasq</li>
<li>Ensure the system is able to execute openQA tests from o3</li>
</ul>