OVHcloud Bare Metal Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[Global][Dedicated Servers] - SSH key migration
Scheduled Maintenance
Report for Bare Metal Cloud
Completed
The scheduled maintenance has been completed.
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled
As part of our continuous improvement plan, maintenance is scheduled on our infrastructure offer.
Start time : 28/05/2024 08:30 UTC
End time : 28/05/2024 08:45 UTC
Service impact : None
Service improvement : SSH key-based authentication behavior change on Linux rescue for dedicated servers
You can ignore this message in one of the following situations:
- you don't know what a Linux rescue is,
- you are using OVHcloud control panel rather than OVHcloud API to boot your dedicated server into Linux rescue,
- you are using password-base rather than ssh key-based authentication when booting your dedicated server into Linux rescue.
We have simplified the mechanism used to configure SSH key-based authentication when booting you server into Linux rescue mode.
In the past, SSH key-based authentication was used with the default SSH key associated to your nic.
The 13rd of May 2024, we have removed that mechanism and you now need to set the rescueSshKey directly as attribut for every server: PUT /dedicated/server/{serviceName}.
The 28th of May 2024, we will:
- remove the API call PUT /me/sshKey/{keyName} (other API calls of the /me/sshKey/ section will NOT be affected)
- configure for you the rescueSshKey for all servers belonging to a nic with a SSH key set as default and if not already done by yourself on this server, so you won't be impacted whenever you decide to reboot your server into rescue.
Note that you will eventually need to perform a change in your provisioning scripts for any newly ordered server to integrate a PUT /dedicated/server/{serviceName} to set the SSH public key.
Start time : 28/05/2024 08:30 UTC
End time : 28/05/2024 08:45 UTC
Service impact : None
Service improvement : SSH key-based authentication behavior change on Linux rescue for dedicated servers
You can ignore this message in one of the following situations:
- you don't know what a Linux rescue is,
- you are using OVHcloud control panel rather than OVHcloud API to boot your dedicated server into Linux rescue,
- you are using password-base rather than ssh key-based authentication when booting your dedicated server into Linux rescue.
We have simplified the mechanism used to configure SSH key-based authentication when booting you server into Linux rescue mode.
In the past, SSH key-based authentication was used with the default SSH key associated to your nic.
The 13rd of May 2024, we have removed that mechanism and you now need to set the rescueSshKey directly as attribut for every server: PUT /dedicated/server/{serviceName}.
The 28th of May 2024, we will:
- remove the API call PUT /me/sshKey/{keyName} (other API calls of the /me/sshKey/ section will NOT be affected)
- configure for you the rescueSshKey for all servers belonging to a nic with a SSH key set as default and if not already done by yourself on this server, so you won't be impacted whenever you decide to reboot your server into rescue.
Note that you will eventually need to perform a change in your provisioning scripts for any newly ordered server to integrate a PUT /dedicated/server/{serviceName} to set the SSH public key.
This scheduled maintenance affected: Dedicated Servers || Operating System (Zone Europe, Zone APAC, Zone Canada).