action #153709
closedcoordination #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 - ada size:M
0%
Description
Acceptance criteria¶
- AC1: ada is usable from PRG2e - QA engineers can access the machine using virt-manager as well as their personal VMs over ssh
- AC2: ada is stable in our salt again
Suggestions¶
- DONE Follow https://jira.suse.com/browse/ENGINFRA-3685
- Ensure machine can be reached, e.g. ssh, IPv4+IPv6
- Ensure machine is used as in before migration including VMs
- After ensuring system is fully up,
systemctl is-system-running, then add back to salt and ensure there are no related alerts
Updated by okurz 9 months ago
- Copied from action #153706: Move of selected LSG QE machines NUE1 to PRG2 - amd-zen2-gpu-sut1 size:M added
Updated by okurz 9 months ago
- Copied to action #153715: Move of LSG QE non-openQA PowerPC machine NUE1 to PRG2 - whale added
Updated by okurz 8 months ago
(Jacek Rybicki) IPv4 implemented, please test the server connecitivity
(Oliver Kurz) I can confirm that ada.qe.prg2.suse.org and ada.qe.suse.de can be reached over IPv4 so far.
https://suse.slack.com/archives/C02CANHLANP/p1707134893024639
@here to all users of ada.qe.suse.de, you won't believe it but it's back up. So far reachable only over IPv4 so expect more disruptions until the machine is fully reachable and again properly monitored by us. Until then feel welcome to try to connect to ada directly or the VMs running on it.
Updated by okurz 8 months ago
- Status changed from Blocked to New
- Assignee deleted (
okurz)
IPv6 address is allocated by SLAAC, please check IPv6 settings on ada server, compare NIC settings with for example with fibonacci server (https://racktables.suse.de/index.php?page=object&object_id=10902) where IPv6 address is reachable and allocated the same (SLAAC)
Updated by okurz 8 months ago · Edited
- Status changed from Blocked to In Progress
IPv6 on ada now working fine. I added ada to salt and applied a high state. No problems there. Updating workerconf. The current IPMI password has some hard to handle characters included so I added another ipmi account similar to other PRG2 machines:
ipmitool -I lanplus -H ada.qe-ipmi-ur -U ADMIN -P … user set name 3 qadmin
ipmitool -I lanplus -H ada.qe-ipmi-ur -U ADMIN -P … user set password 3
ipmitool -I lanplus -H ada.qe-ipmi-ur -U ADMIN -P … channel setaccess 1 3 link=on ipmi=on callin=on privilege=4
ipmitool -I lanplus -H ada.qe-ipmi-ur -U ADMIN -P … user enable 3
https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/728 (merged)
sol activate can establish a connection but I couldn't see any output despite starting getty@ttyS0, …S1, …S2
nevermind. I did screen /dev/ttyS1 115200, conducted a successful echo test and now systemctl enable --now serial-getty@ttyS1 shows a prompt on the serial output. I guess the installation was conducted without configuring the serial port so neither grub nor linux nor getty shows up yet.
So in /etc/default/grub I set
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS1,115200…"
GRUB_SERIAL_COMMAND="serial --unit=1 --speed=115200"