Project

General

Profile

Actions

action #43937

closed

align o3 workers (done: "imagetester" and) "power8" with the others which are currently "transactional-update" hosts

Added by okurz over 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2018-11-15
Due date:
% Done:

0%

Estimated time:

Description


Related issues 3 (1 open2 closed)

Related to openQA Project - coordination #43934: [epic] Manage o3 infrastructure with salt againBlockedokurz2021-03-16

Actions
Related to openQA Infrastructure - action #53525: Upgrade o3 workers to Leap 15.1Resolvedokurz2019-06-262019-07-20

Actions
Copied to openQA Infrastructure - action #43976: bring o3 to same OS (or salt) version as workers, e.g. openSUSE Leap 15.0Resolvedokurz2018-11-152019-07-05

Actions
Actions #1

Updated by okurz over 5 years ago

Actions #2

Updated by okurz over 5 years ago

  • Copied to action #43976: bring o3 to same OS (or salt) version as workers, e.g. openSUSE Leap 15.0 added
Actions #3

Updated by nicksinger over 5 years ago

  • Status changed from New to Workable
Actions #4

Updated by nicksinger over 5 years ago

Actions #5

Updated by nicksinger over 5 years ago

Actions #6

Updated by okurz almost 5 years ago

  • Subject changed from align o3 workers "imagetester" and "power8" with the others which are currently "transactional-update" hosts to align o3 workers (done: "imagetester" and) "power8" with the others which are currently "transactional-update" hosts
Actions #7

Updated by okurz almost 5 years ago

imagetester was reinstalled some months ago now with also being "transactional".

Actions #8

Updated by okurz almost 5 years ago

Actions #9

Updated by okurz almost 5 years ago

Actions #10

Updated by okurz almost 5 years ago

  • Priority changed from Normal to Urgent

this is getting urgent now as power8.o.o is still Leap 42.3 which goes EOL this month. Without access to any management interface I would not dare to upgrade.

Actions #11

Updated by okurz almost 5 years ago

  • Assignee set to nicksinger

@nicksinger could you please help with your social engineering skills or "good connections" to learn about management interface access to power8 (and also o3)?

Actions #12

Updated by okurz almost 5 years ago

  • Status changed from Workable to In Progress
  • Assignee changed from nicksinger to okurz

On power8, as I still do not know about any MC access I did

# ipmitool lan print
Set in Progress         : Set Complete
IP Address Source       : DHCP Address
IP Address              : 10.160.1.104
Subnet Mask             : 255.255.0.0
MAC Address             : 98:be:94:4b:8e:98
Default Gateway IP      : 10.160.255.254
Cipher Suite Priv Max   : Not Available
Bad Password Threshold  : Not Available

so it's 10.160.1.104 which relates to openqaworker-power8-ipmi.suse.de . So far so good but the usual credentials do not work for a SOL. Following https://www.thomas-krenn.com/en/wiki/Configuring_IPMI_under_Linux_using_ipmitool#User_Configuration I just did that myself now using

ipmitool user set name 2 ADMIN
ipmitool user set password 2
<enter password>
ipmitool channel setaccess 1 2 link=on ipmi=on callin=on privilege=4
ipmitool user enable 2

Added to
https://confluence.suse.com/display/openqa/openQA

Actions #13

Updated by okurz almost 5 years ago

Notified on #opensuse-factory:

[24/06/2019 13:39:12] <okurz> michel_mno: I got IPMI (management interface) to power8.o.o now, will do an update/reboot/upgrade over the course of this and maybe next week

What I did on power8:

cd /etc/zypp/repos.d/
mv devel_openQA_Leap{_42.2,}.repo 
sed -i 's/42\.3/15.1/g' *
zypper ref
zypper patch --updatestack-only && zypper -n dup --auto-agree-with-licenses --replacefiles --download-in-advance
for i in $(cat /var/adm/rpmconfigcheck) ; do vimdiff $i ${i%.rpm*}; done
rm $(cat /var/adm/rpmconfigcheck)
rpmconfigcheck
reboot

Monitored that the bootup works fine over IPMI interface. Then triggered a job on o3 for ppc64le, started https://openqa.opensuse.org/tests/966916 . Seems to be fine. So upgraded to Leap 15.1 but not reinstalled as transactional system.

Actions #14

Updated by okurz almost 5 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)
  • Priority changed from Urgent to Normal
Actions #15

Updated by okurz almost 5 years ago

  • Related to action #53525: Upgrade o3 workers to Leap 15.1 added
Actions #16

Updated by okurz almost 5 years ago

  • Subject changed from align o3 workers (done: "imagetester" and) "power8" with the others which are currently "transactional-update" hosts to Convert "power8.o.o" to "transactional server to align with other o3 workers
Actions #17

Updated by okurz over 4 years ago

  • Subject changed from Convert "power8.o.o" to "transactional server to align with other o3 workers to align o3 workers (done: "imagetester" and) "power8" with the others which are currently "transactional-update" hosts
  • Status changed from Workable to Resolved
  • Assignee set to okurz

Actually I am pretty happy with the setup as-is. The other workers are transactional, power8 is not but also automatically updated. This did not seem to pose any problems so far. I don't think we need to go the extra mile and make power8 transactional as well

Actions

Also available in: Atom PDF