Project

General

Profile

Actions

action #153703

closed

coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability

coordination #153685: [epic] Move from SUSE NUE1 (Maxtorhof) to PRG2e

Move of selected LSG QE machines NUE1 to PRG2e - voyager

Added by okurz 12 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Start date:
2024-01-16
Due date:
% Done:

0%

Estimated time:

Description

Acceptance criteria

  • AC1: voyager is usable from PRG2e

Suggestions

Actions #3

Updated by okurz 12 months ago

  • Status changed from New to Blocked
Actions #4

Updated by okurz 11 months ago

  • Description updated (diff)
Actions #5

Updated by pluskalm 11 months ago

List of vm's (and possibly some stray physical machines) in qam nue

refdb arch=x86_64|grep suse.de|awk '{print $2}'

name=asriel.qam.suse.de
name=aziraphale.qam.suse.de
name=barbara.qam.suse.de
name=belle.qam.suse.de
name=deborah.qam.suse.de
name=fricka.qam.suse.de
name=gabriel.qam.suse.de
name=geordi.qam.suse.de
name=giant.qam.suse.de
name=glinda.qam.suse.de
name=gorgon.qam.suse.de
name=halley.qam.suse.de
name=judith.qam.suse.de
name=kathryn.qam.suse.de
name=naix.qam.suse.de
name=omniknight.qam.suse.de
name=roke.qam.suse.de
name=seven.qam.suse.de
name=snowhite.qam.suse.de
name=teradata1.qam.suse.de
name=teradata2.qam.suse.de

Actions #6

Updated by okurz 10 months ago

  • Status changed from Blocked to In Progress
  • Target version changed from future to Ready
Actions #7

Updated by okurz 10 months ago · Edited

I resolved https://jira.suse.com/browse/ENGINFRA-3742 and with a cracking attempt I could decipher the IPMI credentials

Actions #9

Updated by okurz 10 months ago · Edited

  • Due date set to 2024-03-13
  • Status changed from In Progress to Feedback

https://suse.slack.com/archives/C02CANHLANP/p1709125718981899

Related to https://suse.slack.com/archives/C02CANHLANP/p1708520004766399 who can provide me ssh credentials for voyager.qe.prg2.suse.org? (CC @Martin Pluskal)
send me your ssh key ... or alternatively put your key to sshkeys yml at qa-maintenance/templates-management and you will get it distributed in lot of places
https://gitlab.suse.de/qa-maintenance/templates-management/-/merge_requests/89
approved
cron rund every 3 hours afaik

Actions #10

Updated by okurz 10 months ago

  • Status changed from Feedback to Blocked

pluskalm wrote in #note-5:

List of vm's (and possibly some stray physical machines) in qam nue
name=asriel.qam.suse.de
name=aziraphale.qam.suse.de
name=barbara.qam.suse.de
name=belle.qam.suse.de
name=deborah.qam.suse.de
name=gabriel.qam.suse.de
name=geordi.qam.suse.de
name=giant.qam.suse.de
name=glinda.qam.suse.de
name=gorgon.qam.suse.de
name=halley.qam.suse.de
name=judith.qam.suse.de
name=kathryn.qam.suse.de
name=naix.qam.suse.de
name=omniknight.qam.suse.de
name=roke.qam.suse.de
name=seven.qam.suse.de
name=snowhite.qam.suse.de
name=teradata1.qam.suse.de
name=teradata2.qam.suse.de

Added all plus "crowley" with
https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4799

name=fricka.qam.suse.de

https://racktables.nue.suse.com/index.php?page=object&object_id=13685 , decommissioned physical machine in nue2.

In the meantime I could login as root after my ssh key was apparently deployed. With this I saw the above machines already running. Let's await the static DHCP lease config https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4799 merged and then I will check if machines get a valid address and the right ones as well.

Actions #11

Updated by okurz 10 months ago

  • Status changed from Blocked to In Progress

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4799 is merged. I called

nmap -sn asriel.qe.prg2.suse.org aziraphale.qe.prg2.suse.org barbara.qe.prg2.suse.org belle.qe.prg2.suse.org deborah.qe.prg2.suse.org gabriel.qe.prg2.suse.org geordi.qe.prg2.suse.org giant.qe.prg2.suse.org glinda.qe.prg2.suse.org gorgon.qe.prg2.suse.org halley.qe.prg2.suse.org judith.qe.prg2.suse.org kathryn.qe.prg2.suse.org naix.qe.prg2.suse.org omniknight.qe.prg2.suse.org roke.qe.prg2.suse.org seven.qe.prg2.suse.org snowhite.qe.prg2.suse.org teradata1.qe.prg2.suse.org teradata2.qe.prg2.suse.org but so far no machines are up with the according addresses:

Starting Nmap 7.92 ( https://nmap.org ) at 2024-03-05 14:14 CET
Nmap done: 20 IP addresses (0 hosts up) scanned in 9.56 seconds

Triggered a reboot of the machine

Actions #12

Updated by okurz 10 months ago · Edited

https://suse.slack.com/archives/C02CANHLANP/p1709645194783289

@Martin Pluskal IMHO voyager.qe.prg2.suse.org and VMs on it are fully up and running now:

Nmap scan report for aziraphale.qe.prg2.suse.org (10.146.4.52)
Host is up (0.061s latency).
Nmap scan report for barbara.qe.prg2.suse.org (10.146.4.53)
Host is up (0.061s latency).
Nmap scan report for deborah.qe.prg2.suse.org (10.146.4.56)
Host is up (0.061s latency).
Nmap scan report for gabriel.qe.prg2.suse.org (10.146.4.57)
Host is up (0.061s latency).
Nmap scan report for judith.qe.prg2.suse.org (10.146.4.63)
Host is up (0.051s latency).
Nmap scan report for roke.qe.prg2.suse.org (10.146.4.67)
Host is up (0.052s latency).

Can you confirm everything is as expected or is there more I could help with?

Actions #13

Updated by okurz 10 months ago

  • Due date deleted (2024-03-13)
  • Status changed from In Progress to Resolved

Updated the description on https://racktables.nue.suse.com/index.php?page=object&tab=default&object_id=15335 . No further feedback received, assuming ok. If there are problems in the future we will learn about it.

Actions

Also available in: Atom PDF