openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-09-20T07:33:04ZopenSUSE Project Management Tool
Redmine openQA Infrastructure - action #136115 (Resolved): https://racktables.nue.suse.com/ yields "Datab...https://progress.opensuse.org/issues/1361152023-09-20T07:33:04Zokurzokurz@suse.com
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p><a href="https://racktables.nue.suse.com/" class="external">https://racktables.nue.suse.com/</a> yields "Database write failed - LDAP caching error" on connection attempts after about 1m waiting time</p>
<a name="Steps-to-reproduce"></a>
<h2 >Steps to reproduce<a href="#Steps-to-reproduce" class="wiki-anchor">¶</a></h2>
<ul>
<li>With your browser go to <a href="https://racktables.nue.suse.com/" class="external">https://racktables.nue.suse.com/</a></li>
<li>If you are asked for username+password enter the credentials and confirm</li>
<li>Observe the browser being busy waiting for a reply</li>
<li>Observe after about 1m the error message "Database write failed - LDAP caching error"</li>
</ul>
QA - action #125147 (Resolved): Nuremberg QA workstations and QAM labs cold storage move to Frank...https://progress.opensuse.org/issues/1251472023-02-28T12:46:29Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Rent at Maxtorhof will end. The new location at Nbg Frankencampus will have lab rooms in the same building where the office rooms are. We must prepare and execute the move of QAM equipment from the old location, mostly <a href="https://racktables.nue.suse.com/index.php?page=rack&tab=default&rack_id=18018" class="external">NUE-2.2.10 QA cold storage</a> to an according Frankencampus room</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> There is no more QA/QAM equipment in Maxtorhof office rooms or <a href="https://racktables.nue.suse.com/index.php?page=rack&tab=default&rack_id=18018" class="external">NUE-2.2.10</a> and <a href="https://racktables.nue.suse.com/index.php?page=rack&tab=default&rack_id=19899" class="external">NUE-2.2.13</a> physically</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><em>DONE</em> <del>Ask for objections</del> -> no objections</li>
<li>Organize transport of still usable equipment: Create ticket over <a href="https://sd.suse.com" class="external">https://sd.suse.com</a> to component "Facilities" asking them to move the equipment to FC Basement</li>
<li><em>Optional/nice-to-have</em> visit the Maxtorhof place beforehand and prepare the move better, e.g. nothing connected anymore, packed into boxes or something</li>
<li>Scrap decommissioned hardware, see <a href="https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs#How_to_decommission_and_dispose_old_hardware" class="external">https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs#How_to_decommission_and_dispose_old_hardware</a></li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>The above tasks shouldn't need anyone from our team on-site but it would be helpful to first check in-site and disconnect the workstations that are still connected.</p>
QA - action #125144 (Resolved): Give members of SUSE QE Tools team a chance to get familiar with ...https://progress.opensuse.org/issues/1251442023-02-28T12:31:36Zlivdywanliv.dywan@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>We agreed to take over consistent maintainership of those machines and should be sure we know what we're signing up for.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The SUSE QE Tools team knows the basics about the Nbg QAM machines and feels in a position to make relevant decisions</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>With the whole team walk over all machines in racktables to get accustomed.</li>
<li>Conduct a mob session with multiple team members (in the regular slot or ad-hoc, whichever is convenient)</li>
</ul>
QA - action #124724 (Resolved): Ensure Nbg QAM machines have a current maintainer as "contact per...https://progress.opensuse.org/issues/1247242023-02-17T09:24:36Zokurzokurz@suse.com
<p>Ensure Nbg QAM machines have a current maintainer as "contact person"</p>
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>With the work on <a class="issue tracker-6 status-3 priority-4 priority-default closed child parent" title="coordination: [epic] Migration of SUSE Nbg based openQA+QA+QAM systems to new security zones (Resolved)" href="https://progress.opensuse.org/issues/116623">#116623</a> it became clear that we want to have any QAM machines now treated as a joint "QE" group, including not only IP range, domain, etc., but also physical machines, their maintainership and administration. With this we should ensure that all former Nbg QAM machines are maintained by the SUSE QE Tools team. The SUSE QE Tools team will take responsibility, ensure maintainership, make decisions. This was also clarified with the line managers of the former contact persons who like to focus on other areas of work.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1</strong>: All former Nrg QAM machines are visibly owned by the QE Tools Team</li>
</ul>
<a name="Acceptance-tests"></a>
<h2 >Acceptance tests<a href="#Acceptance-tests" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AT1:</strong> <a href="https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=dabatianni" class="external">https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=dabatianni</a> and <a href="https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=apappas" class="external">https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=apappas</a> are empty</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>We clarified that it's a better option to update the racktables entries to "<a href="mailto:qa-team@suse.de">qa-team@suse.de</a>" with a comment pointing to the former "contact person" who can still be asked for information or specific help.</li>
</ul>
<p>Suggestion for comment in racktables to include: 2023-02-28: This machine was formerly maintained by dabatianni+apappas from QA Maintenance. Feel free to contact them for specific questions regarding the former use of those machines.</p>
QA - coordination #124721 (Resolved): [epic] Ensure proper QE maintainership of Nbg QAM machineshttps://progress.opensuse.org/issues/1247212023-02-17T09:20:24Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>With the work on <a class="issue tracker-6 status-3 priority-4 priority-default closed child parent" title="coordination: [epic] Migration of SUSE Nbg based openQA+QA+QAM systems to new security zones (Resolved)" href="https://progress.opensuse.org/issues/116623">#116623</a> it became clear that we want to have any QAM machines now treated as a joint "QE" group, including not only IP range, domain, etc., but also physical machines, their maintainership and administration. With this we should ensure that all former Nbg QAM machines are maintained by the SUSE QE Tools team. The SUSE QE Tools team will take responsibility, ensure maintainership, make decisions. This was also clarified with the line managers of the former contact persons who like to focus on other areas of work.</p>
<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://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=dabatianni" class="external">https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=dabatianni</a> and <a href="https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=apappas" class="external">https://racktables.nue.suse.com/?page=search&last_page=search&last_tab=default&q=apappas</a> are empty</li>
<li><strong>AC2:</strong> The SUSE QE Tools team knows the basics about the Nbg QAM machines and feels in a position to make relevant decisions</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>We clarified that it's a better option to update the racktables entries to "<a href="mailto:qa-team@suse.de">qa-team@suse.de</a>" with a comment pointing to the former "contact person" who can still be asked for information or specific help.</li>
<li>With the whole team walk over all machines in racktables to get accustomed.</li>
<li>Where we see the need plan according work, e.g. to move some machines and such.</li>
</ul>