[Completed][Hazard Notice] [monash-02] Hard-reboot the instances with volume attached
S
Shahaan Ayyub
started a topic
over 2 years ago
Dear Nectar User(s),
As part of continuous upgrade, monash-02 computational storage(volume storage) has been migrated to the new infrastructure.
Impact:
We do not anticipate disruption to the volume service, however due to the changes in the infrastructure, we strongly recommend to hard-reboot the instances with volume attached to refresh the state. Until you have hard-rebooted the instance, the instance may encounter an error when you reboot(soft) the instance.
The instances without volume attached are not affected and not required to be rebooted.
Thank you for your cooperation.
We apologise for the inconvenience caused due to this issue.
Shahaan Ayyub
Dear Nectar User(s),
As part of continuous upgrade, monash-02 computational storage(volume storage) has been migrated to the new infrastructure.
Impact:
We do not anticipate disruption to the volume service, however due to the changes in the infrastructure, we strongly recommend to hard-reboot the instances with volume attached to refresh the state. Until you have hard-rebooted the instance, the instance may encounter an error when you reboot(soft) the instance.
The instances without volume attached are not affected and not required to be rebooted.
Thank you for your cooperation.
We apologise for the inconvenience caused due to this issue.
Kind regards,
Research Cloud at Monash