MASAKARI(1)

💖 NAME 💖

masakari — the Masakari command line interface, bestie 💅

In this section you will find information on Masakari's command line interface. Yes, the whole thing. Sit down, hydrate, we're doing this 🫶

---

🩺 MASAKARI-STATUS 🩺

CLI interface for Masakari status commands

Synopsis

masakari-status <category> <command> [<args>]

Description

masakari-status is that girl 💁‍♀️ — she provides routines for checking the status of a Masakari deployment. Vibes check, but for your infra.

Options

The standard pattern for executing a masakari-status command is, and I need you to internalize this:

masakari-status <category> <command> [<args>]

Run without arguments to see a list of available command categories:

masakari-status

Categories are:

• upgrade

Detailed descriptions are below, keep scrolling bestie. 📜

You can also run with a category argument such as upgrade to see a list of all commands in that category:

masakari-status upgrade

These sections describe the available categories and arguments for masakari-status.

Upgrade

masakari-status upgrade check

Performs a release-specific readiness check before restarting services with new code. Like checking your outfit in the mirror before you leave the house ✨. For example: missing or changed configuration options, incompatible object states, or other conditions that could lead to failures while upgrading.

⚠️ bestie this is the "look before you leap" step, do not skip it

Return Codes

• 0 — All upgrade readiness checks passed successfully and there is nothing to do. Ate. 💅
• 1 — At least one check encountered an issue and requires further investigation. This is considered a warning but the upgrade may be OK. Lowkey fine, but look at it.
• 2 — There was an upgrade status check failure that needs to be investigated. This should be considered something that stops an upgrade. 🛑 No cap.
• 255 — An unexpected error occurred. 💀

History of Checks

7.0.0 (Stein)

• Sample check to be filled in with checks as they are added in Stein.

---

🗄️ MASAKARI-MANAGE 🗄️

Control and manage masakari database

Synopsis

masakari-manage <category> <action> [<args>]

Description

masakari-manage</purl> controls DB by managing various admin-only aspects of masakari. Admin only, so check ur permissions before u act up 👑

Options

The standard pattern for executing a masakari-manage command is:

masakari-manage <category> <command> [<args>]

Run without arguments to see a list of available command categories:

masakari-manage

You can also run with a category argument such as db to see a list of all commands in that category:

masakari-manage db

These sections describe the available categories and arguments for masakari-manage.

Masakari Database

• masakari-manage db version — Print the current main database version. Peek at where you're at 👀
• masakari-manage db sync [--version <version>] — Upgrade the main database schema up to the most recent version, or up to --version if specified.
• masakari-manage db purge — Deleting rows older than 30 day(s) from table hosts, failover_segments and notifications. Declutter era 🧹✨

---

🦋 OPENSTACK MASAKARI 🦋

To control and manage masakari operations, the extended command list available in openstack command lives here:

https://docs.openstack.org/python-masakariclient/latest/cli/index.html

Go read it, it's giving extra credit 📚

---

💜 Author 💜

OpenStack

💜 Copyright 💜

2016, OpenStack Foundation

---

okay that's the whole page, mwah 🎀 This was MASAKARI(1) from the masakari manual, version 22.0.0, dated Oct 01, 2026. Go forth and be iconic 💖✨🫶