Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action required: Planned maintenance for Azure will impact virtual machines in West US #4907

Open
3 tasks
dougbu opened this issue Feb 4, 2025 · 1 comment
Open
3 tasks
Labels
Email Notice Operations Used by FR to track issues related to operations work

Comments

@dougbu
Copy link
Member

dougbu commented Feb 4, 2025

received an email w/ this title on 28 January

Details

Node maintenance may affect one or more of your virtual machines in West US
You're receiving this notice because you currently use Azure Virtual Machines.
You've been identified as a customer using virtual machines in West US who may experience connection failures and network latency when attempting to access some virtual machines hosted in the region.
Due to failing hardware, planned maintenance is being scheduled starting at 13 February 2025 23:10 UTC until 14 February 2025 23:10 UTC. To minimize risk to your service, and in case the hardware fails before the system-initiated migration occurs, we recommend that you redeploy your virtual machine(s) prior to 13 February 2025 23:10 UTC.
During this maintenance window, IaaS virtual machines will be migrated to newer network hardware. Please expect each virtual machine to be unavailable for up to 15 minutes after initiating the maintenance. Operating system and data disks will be retained, but temporary disks will be reset.
See a list of your affected virtual machines in the Account Information section of this message.
For more control over when your virtual machines will be affected, migrate your deployments using the Azure portal or PowerShell by following the steps below. You must complete the migration prior to 13 February 2025 23:10 UTC.
Migrate using the Azure portal
For both Classic and Azure Resource Manager Virtual Machines:

  1. Log into the Azure portal and navigate to the virtual machines you want to migrate.
  2. Select "Stop" to stop and deallocate the Virtual Machine. Please ensure the virtual machine status has transitioned to "Stop (deallocated)".
  3. Select "Start" only after the previous change in status has completed.
    For virtual machine scale sets:
  4. Log into the Azure portal and navigate to the virtual machine scale sets.
  5. Select virtual machine scale sets, and select "Instances" from the left-side settings menu.
  6. Select the virtual machine you want to migrate.
  7. Select "Deallocate" to stop and deallocate the virtual machine. Please ensure the virtual machine status has transitioned to "Stop (deallocated)".
  8. Select "Start" only after the previous change in status has completed.
    Migrate using PowerShell
    In Azure PowerShell, invoke the command to stop an Azure Virtual Machine without a "StayProvisioned" flag.
    Example: Stop-AzureVM -ServiceName $cloudServiceName -Name $vmName
    Learn more about stopping an Azure Virtual Machine.
    More information
    Types of maintenance performed on virtual machines
    Receive a notification in your virtual machine 15 minutes prior to reboot
    Support options
    • Ask questions in the Azure Virtual Machines forums.
    • Request support via @AzureSupport or the Azure portal.
    You can view this notification in the Azure portal under event ID: 8MD2-NR8.

Account Information

Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_159829
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _windows.10.amd64.open.rt-a-scaleset_401199
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.android.34.open.rt-a-scaleset_219
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _windows.10.amd64.open.rt-a-scaleset_401058
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_159639
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.android.25.open.rt-a-scaleset_3580
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_158885
Subscription ID: f8c1f536-2a9b-41ba-9868-811cc982bb25
Subscription name: DNCENGHELIX-01
Resource name: _ubuntu.2204.amd64.open.rt-a-scaleset_158935
Subscription ID: a6ad62fb-177e-40ef-af51-5c342911ebf5
Subscription name: DNCENGHELIX-02
Resource name: _windows.10.amd64.open.svc-a-scaleset_368796

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

@dougbu dougbu added the Operations Used by FR to track issues related to operations work label Feb 4, 2025
@dougbu
Copy link
Member Author

dougbu commented Feb 4, 2025

I doubt we have many VMs that won't be automatically migrated before this maintenance window. if there are a few known ones, we could be proactive about them

more likely this will have no impact at all. created the issue primarily to remind us in case problems emerge in the given timeframe. won't be great if the First Responders channel lights up but we'll know where to head to remedy the situation based on reports there (if any)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Email Notice Operations Used by FR to track issues related to operations work
Projects
None yet
Development

No branches or pull requests

1 participant