[Update: 17:10] Hardware logs have been handed over to vendor support for review. At this time it appears that a hardware failure on the hypervisor node delayed I/O and caused the guests to automatically reboot on other hypervisors.
At approximately 16:25 on 11 July 2020 the following systems rebooted due to a crash of the underlying hypervisor. We are still investigating and more will be posted here.
alexandrovlab-ftp.ucsd.edu
athena.sdsc.edu
biobigdata.ucsd.edu
buchhalter.sdsc.edu
caice.sdsc.edu
cloud-web-util
cycoreci2beta.sdsc.edu
EDC-Data-01
exec01.communityhub.hubzero.org
exec01.smarteragriculture.org
flour.sdsc.edu
hiv.sdsc.edu
kambei
massive2
neurores.ucsd.edu
nx-test
osc-dev.ucsd.edu
portaldev.sdsc.edu
richlab-sftp.sdsc.edu
sc-commserve11
sc-locker
sc-watcher
scatter2.dev.nanohub.org
som-sas.ucsd.edu
stage.communityhub.hubzero.org
stage.mcrn.hubzero.org
stage.sciencegateways.org
Trampoline
UNICRON
web-cybernmr2
web01.int.demo.hubzero.org
web01.int.mygeohub.org
web01.int.purr.hubzero.org
webstr
yellowfin.sdsc.edu
yk-test
zfs-test7