IBM Cloud: Host Migration - Customer Action required

[richardlau]

Notification from IBM Cloud:

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 below 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.

NOTE - WINDOWS CUSTOMERS will need to follow additional steps (detailed below) prior to migration to avoid data loss and downtime.

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 selectable. 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 andperform 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.

|

Device Name	Public IP
release-ibm-rhel8-x64-2.nodejs.cloud	50.97.245.10

[richardlau]

I've taken release-ibm-rhel8-x64-2 offline in ci-release. It is currently busy running an iojs+release job -- I'll wait for that to complete and then attempt the migration step.
In the worst case scenario we still have the other IBM Cloud hosted RHEL8 x64 release machine and another hosted on Digital Ocean.

[richardlau]

I've clicked the "Migrate Host" action in the IBM Cloud web console.

[richardlau]

Migration complete. This is still in San Jose, so the action to move it by April 2024 still applies: #3279