https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-07-29T07:09:23ZopenSUSE Project Management ToolopenQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=3153632020-07-29T07:09:23Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Ready</i></li></ul> openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=3168402020-08-06T11:34:12Zokurzokurz@suse.com
<ul><li><strong>Tags</strong> changed from <i>caching, openQA, sporadic, arm, ipmi, worker</i> to <i>worker</i></li></ul> openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=3326172020-10-09T07:31:01Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul><p>upgrading firmware might help but a workaround was found, the bug was resolved as WONTFIX and likely powerKVM has no future. Removing from our backlog</p>
openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=3532082020-11-23T08:39:49Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Blocked</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>Tracking as <a href="https://infra.nue.suse.com/SelfService/Display.html?id=180841" class="external">https://infra.nue.suse.com/SelfService/Display.html?id=180841</a></p>
openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=4042242021-05-05T18:18:53Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-3 priority-lowest closed" href="/issues/65130">action #65130</a>: Upgrade of firmware(s) for cloudberry (power9 machine)</i> added</li></ul> openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=4042302021-05-05T18:20:04Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Feedback</i></li></ul><p><a href="https://infra.nue.suse.com/SelfService/Display.html?id=180841" class="external">https://infra.nue.suse.com/SelfService/Display.html?id=180841</a> was resolved without any proper comment by gschlotter. What I remember is that nicksinger asked me to hold my feet still while he tries to resolve the situation :)</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/24624">@nicksinger</a> I would appreciate your feedback on the current situation.</p>
openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=4044792021-05-06T09:15:03Znicksingernsinger@suse.com
<ul></ul><p>I tried to find my comment regarding my efforts upgrading QA-Power8-5 - couldn't find it. Basically I fail to upload the firmware onto the machine because the required toolchain is so old that I can't build a functional <code>pflash</code> for the BMC of these machines (glibc was too old on these BMCs). Somebody on the ML offered me a binary which is supposed to work but I really don't want to execute a random binary sent from somebody on a mailinglist which is accessing the BMC of our machines. So I'm currently stuck and out of ideas how to continue with these habanero machines.</p>
openQA Infrastructure - action #58325: Update firmware of our powerKVM machines (QA-Power8-3, QA-Power8-4, QA-Power8-5)https://progress.opensuse.org/issues/58325?journal_id=4075092021-05-15T21:03:52Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Rejected</i></li></ul><p>As discussed with nsinger we are not aware of further problems after we fixed the boot problems software side in <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: powerqaworker-qam-1 fails to come up on reboot (repeatedly) (Resolved)" href="https://progress.opensuse.org/issues/68053">#68053</a> so we can also close this ticket as rejected as we did not conduct the firmware upgrades.</p>