search

nodejs / build

Better build and test infra for Node.
503 stars 165 forks source link

Cloud Host Migration - Customer Action required #3804

Closed richardlau closed 2 months ago

richardlau commented 2 months ago 
ID:161865893
Type:Planned Event
Subject:Upcoming Planned Cloud Maintenance
Start Date:08-Aug-2024 07:00 UTC (Aug 08, 2024 02:00AM CDT)
End Date:08-Aug-2024 11:00 UTC (Aug 08, 2024 06:00AM CDT)
Duration:4 Hours
Event Description
Subject: Cloud Host Migration - Customer Action required

*** This is a system generated ticket, please do not reply. Please contact support for any assistance. ***

IBM Cloud engineers are conducting a technology refresh project aimed at increasing the cloud host stability and reliability. Customers who are receiving this maintenance ticket have Virtual Server Instances (VSIs) on cloud hosts which are scheduled to be emptied and updated. The identified VSIs need to be migrated to different cloud hosts in order for IBM Cloud engineers to conduct the maintenance.

Reservations for all affected VSIs have been made on new cloud hosts and customers are asked to self-migrate their VSIs at their convenience before the scheduled date above.
Any VSIs not self-migrated will be automatically migrated beginning at the time above.

NOTES
- WINDOWS CUSTOMERS will need to follow additional steps (detailed below) prior to migration to avoid data loss and downtime.
- NETSCALER / VPX CUSTOMERS cannot self migrate. If you are one of these customers and the time listed above does not work, please open a case with our Cloud Support team for assistance in getting migrated.

ALL OTHER CUSTOMERS:
** To self-migrate your virtual server, go to the "Device List", which can be found under "Devices" across the top of Control Portal, and select "Actions".
A "Migrate Host" option should be now be available. Select this option and your VSI will be migrated to the host reserved for your VSI.
Your VSI self migration will also be initiated automatically if/when the VSI is rebooted next. **

Windows Customers:

ISSUE DESCRIPTION
Issue #1 - Updates to the Xentools client installed on your device may cause BSOD failures during installation if the update is installed using Windows Automatic Update. Please see the following articles for details: https://www.ibm.com/support/pages/node/6462327 & https://support.citrix.com/article/CTX292687/setting-automatic-reboots-when-updating-the-citrix-vm-tools-for-windows

Issue #2 - Xentools must be updated to the latest version in order for your device to be migrated during the above maintenance without going offline.

RISKS: For both issues, IBM support engineers have observed BSOD failures, boot issues, networking failures, and failures during various boot stages during a migration.

NEXT STEPS:
Issue #1 - Disable auto updates for the Xentools package in Windows Update and perform a manual update of Xentools using the following instructions. https://www.ibm.com/support/pages/node/6462327
Issue #2 - Once Xentools is updated to the latest version, migrations to a new platform will no longer be blocked, and can proceed as described above.

We apologize for the inconvenience
IBM Capacity Management.
Devices Affected
Devices that are disabled or no longer available will be visible but inaccessible below.

1-1 of 1 items1 of 1 pages
1

[release-ibm-rhel8-x64-1.nodejs.private](https://cloud.ibm.com/classic/devices/details/47485047/virtualGuest)
richardlau commented 2 months ago

Since we have redundancy, I've requested the migration in the web ui.

richardlau commented 2 months ago

Machine has been migrated and had a successful build on it today.