Project

General

Profile

Actions

action #63142

closed

Upgrade firmware of ppc9 machine redcurrant

Added by nicksinger about 4 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
-
Target version:
Start date:
2020-02-05
Due date:
% Done:

0%

Estimated time:

Description

TODO: check which firmware we actually need (find machine type in e.g. HMC)

  1. RAID controller
  2. Netzwerk controller (? sit together with Toni)
  3. Firmware of machine (can be done from HMC)

Related issues 2 (1 open1 closed)

Related to openQA Infrastructure - action #65130: Upgrade of firmware(s) for cloudberry (power9 machine)Rejectednicksinger2020-04-01

Actions
Related to openQA Infrastructure - action #76951: Check if new firmware for kerosene (aka. power8.o.o) exists and remove os-autoinst workarounds again when according machine settings are applied when necessary size:MWorkable2020-10-25

Actions
Actions #1

Updated by okurz over 3 years ago

  • Priority changed from Normal to Low
Actions #2

Updated by okurz over 3 years ago

  • Target version set to Ready
Actions #3

Updated by okurz over 3 years ago

  • Related to action #65130: Upgrade of firmware(s) for cloudberry (power9 machine) added
Actions #4

Updated by okurz over 3 years ago

  • Target version changed from Ready to future

According to https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/workerconf.sls#L738 we have a machine "redcurrent" in our config and also on https://openqa.suse.de/admin/workers/1326 I see that the machine is running tests just fine. However, you wrote "ppc9" and I assume you meant "power9". But https://openqa.suse.de/admin/workers/1326 says "POWER8". Any ideas why the mismatch?

Still, based on that I assume this is not necessarily needed for us to plan right now.

Actions #5

Updated by okurz over 3 years ago

nsinger will ask aeisner to do that for us

Actions #6

Updated by okurz over 3 years ago

  • Related to action #76951: Check if new firmware for kerosene (aka. power8.o.o) exists and remove os-autoinst workarounds again when according machine settings are applied when necessary size:M added
Actions #7

Updated by okurz over 3 years ago

  • Status changed from New to Workable
  • Assignee set to nicksinger
  • Target version changed from future to Ready

@nicksinger as discussed you will create a ticket to infra and CC osd-admins@suse.de and aeisner

Actions #8

Updated by nicksinger over 3 years ago

I've opened RT-ADM #180857. However I failed to reach aeisner@suse.de as well as aeisner@suse.com so just sending it to infra@suse.de for now… Sorry for the spam

Actions #9

Updated by okurz over 3 years ago

as clickable URL for the ones that have access RT-ADM #180857

Actions #11

Updated by okurz almost 3 years ago

  • Status changed from Workable to Rejected

As discussed with nsinger we are not aware of further problems after we fixed the boot problems software side in #68053 so we can also close this ticket as rejected as we did not conduct the firmware upgrades.

Actions

Also available in: Atom PDF