Skip to content

docs(opcp): warn against rebooting bare-metal instances from the OS #399

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.

Sign up for GitHub

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

Open
AlexandreHelmer wants to merge 2 commits into
base: develop
Choose a base branch
from
+48 −2
Open

docs(opcp): warn against rebooting bare-metal instances from the OS #399

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
142e916
docs(opcp): warn against rebooting bare-metal instances from the OS
AlexandreHelmer Jul 15, 2026
9fb0bc0
docs(opcp): narrow reboot warning to shutdown and add Ironic workaround
AlexandreHelmer Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 23 additions & 1 deletion docs/en/guides/hosted-private-cloud/opcp/how-to-setup-instance-from-cli.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: How to Deploy an Instance via the OpenStack CLI
description: Find out how to deploy an OPCP instance via the OpenStack command-line interface by configuring networks, subnets, instances, and SSH keys
lastUpdated: 2026-06-16
lastUpdated: 2026-07-15
---

## Objective
Expand Down Expand Up @@ -343,6 +343,28 @@ You must ensure that the node is `Available` and has the required **traits** to

To check the current state of a node and retrieve its ID, you can consult our documentation: [OPCP Node Lifecycle](/guides/hosted-private-cloud/opcp/node-lifecycle).

#### Rebooting or Stopping an Instance

You can manage your instance's power state directly through the OpenStack API:

```bash
# Soft reboot
openstack server reboot $INSTANCE_ID

# Hard reboot
openstack server reboot --hard $INSTANCE_ID

# Stop the instance
openstack server stop $INSTANCE_ID

# Start the instance
openstack server start $INSTANCE_ID
```

:::warning
Rebooting or stopping an instance must always be done through the OpenStack API (or the Horizon interface), not from within the operating system using commands such as `systemctl reboot` or `systemctl poweroff`. An action performed directly from the OS is not propagated to OpenStack, which would continue to consider the instance as active, leaving it in an inconsistent state between its actual status and the one known by the platform.

@fthiery fthiery Jul 15, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest workaround would be to poweroff the node with ironic and poweron again so Ironic push the node into unlock_wait state

:::

#### Deleting an Instance

You can delete an instance with the following command:
Expand Down
24 changes: 23 additions & 1 deletion docs/fr/guides/hosted-private-cloud/opcp/how-to-setup-instance-from-cli.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Comment installer une instance depuis la CLI OpenStack
description: Découvrez comment déployer une instance OPCP via l'outil en ligne de commande OpenStack en configurant les réseaux, sous-réseaux, instances et clés SSH
lastUpdated: 2026-06-16
lastUpdated: 2026-07-15
---

## Objectif
Expand Down Expand Up @@ -345,6 +345,28 @@ Il faudra cependant vous assurer que le nœud a le statut `Available` et possèd

Pour vérifier l'état actuel du nœud et récupérer son identifiant, vous pouvez consultez notre documentation : [Cycle de vie d'un nœud OPCP](/guides/hosted-private-cloud/opcp/node-lifecycle).

#### Redémarrer ou arrêter une instance

Vous pouvez gérer l'alimentation de votre instance directement depuis les API OpenStack :

```bash
# Redémarrage logiciel (soft reboot)
openstack server reboot $INSTANCE_ID

# Redémarrage matériel (hard reboot)
openstack server reboot --hard $INSTANCE_ID

# Arrêter l'instance
openstack server stop $INSTANCE_ID

# Démarrer l'instance
openstack server start $INSTANCE_ID
```

:::warning
Le redémarrage ou l'arrêt d'une instance doit toujours être effectué depuis l'API OpenStack (ou l'interface Horizon), et non depuis le système d'exploitation via des commandes telles que `systemctl reboot` ou `systemctl poweroff`. Une action réalisée directement depuis l'OS n'est pas propagée à OpenStack, qui continuerait de considérer l'instance comme active : elle se retrouverait dans un état incohérent entre son statut réel et celui connu par la plateforme.
:::

#### Suppression d'une instance

Vous pouvez supprimer une instance grâce à la commande suivante :
Expand Down