Added by ybonatakis 3 days ago. Updated 2 days ago.
0%
Description
I couldnt ssh into worker-arm2 to get any logs, so I have no idea what service failed or what happened
http://monitor.qa.suse.de/goto/9w9845cNR?orgId=1
salt-key --accept=worker-arm2.oqa.prg2.suse.org
Machine + BMC cannot be pinged. Access to documented PDUs in https://racktables.suse.de/index.php?page=object&tab=default&object_id=22943 not possible so creating a SD ticket: https://sd.suse.com/servicedesk/customer/portal/1/SD-180419
Also removing the machine from production according to https://progress.opensuse.org/projects/openqav3/wiki#Take-machines-out-of-salt-controlled-production
nicksinger wrote in #note-3:
Machine + BMC cannot be pinged. Access to documented PDUs in https://racktables.suse.de/index.php?page=object&tab=default&object_id=22943 not possible so creating a SD ticket: https://sd.suse.com/servicedesk/customer/portal/1/SD-180419
How did you try to access the PDUs? Did you follow
https://gitlab.suse.de/suse/wiki/-/blob/main/qe_infrastructure.md#prg2 ?
okurz wrote in #note-5:
nicksinger wrote in #note-3:
Machine + BMC cannot be pinged. Access to documented PDUs in https://racktables.suse.de/index.php?page=object&tab=default&object_id=22943 not possible so creating a SD ticket: https://sd.suse.com/servicedesk/customer/portal/1/SD-180419
How did you try to access the PDUs? Did you follow
https://gitlab.suse.de/suse/wiki/-/blob/main/qe_infrastructure.md#prg2 ?
just by accessing the URL in my browser. Totally forgot about this one, thanks for the reminder. Will power-cycle the BMC now and update SD if needed
Setting due date based on mean cycle time of SUSE QE Tools
Updated the SD ticket with:
I powered down both ports and waited several minutes, however port 22 always shows >0W power. Anyhow, even after a full power-cycle, the BMC does not come back.
So I unfortunately have to ask you if you can check the machine physically if there is any sign of broken hardware or a loose ethernet plug. Thanks!