action #114697
closed
- Status changed from New to Resolved
Clarified with jlausuch: servers to be set up as O3 workers, not yet completed. Idle since 2021-09 when the entries have been setup by gschlotter. The machines are supposed to be dedicated for JeOS with different hypervisors. As necessary we can also move the machines elsewhere as long as we can patch them through to the o3 network with the o3 VLAN 662.
Added this information as log record in both racktable entries.
- Related to action #120264: Conduct the migration of SUSE QA systems (non-tools-team maintained) from Nbg SRV1 to new security zones size:M added
Apparently the blocker for both systems was missing connectivity to the o3 network.
At least orion has connectivity on eth3 meanwhile, so I added it as 192.168.112.20 to /etc/hosts and dnsmasq. SSH is reachable.
andromeda might also have connectivity, but the virtual keyboard in the BMC is broken in a weird way that makes logging into the installed windows impossible and I couldn't get into the BIOS menu or PXE boot either.
Also available in: Atom
PDF