BKR-SYSTEM-RELEASE(1)

📦
version 29.2 · 3 versions
, in epel 9

💖 bkr-system-release(1) — the Beaker girlie's guide 💖

Okay bestie, so this is bkr-system-release, a page from the Beaker manual, section 1. It's short, it's sweet, and it's literally the "okay I'm done, you can have it back" button for reserved systems. Let's go ✨

🌸 NAME 🌸

bkr-system-release — release a reserved Beaker system. That's it, that's the whole vibe. You reserved a machine, now you're giving it back to the pool like a good citizen 🫶

🎀 SYNOPSIS 🎀

bkr system-release [options] <fqdn>...

So it's the command, then [options] (whatever extra flags you want, they're optional, live your life), and then one or more <fqdn>s — those are the fully-qualified domain names of the systems you're releasing. Yes, you can hand back more than one at a time. Iconic 💅

🦋 DESCRIPTION 🦋

This bad boy releases a Beaker system that's been reserved. And how did it get reserved, you ask? Any of these ways, bestie:

  • using bkr system-reserve
  • or the Beaker web UI
  • or the <reservesys/> element in the job XML

Whichever way it got locked down, bkr system-release is what frees it. No cap, that's the whole job. 🔓

✨ OPTIONS ✨

Not a lot going on here, and honestly? Respect. The common bkr options are described in the Options section of bkr(1) — so if you need the full flag menu, that's where you go. This page keeps it minimal 🧚

⭐ EXIT STATUS ⭐

  • Non-zero on error 😭
  • Otherwise zero 💖

That's the whole contract. Zero means we slayed, non-zero means something went sideways.

🔥 EXAMPLES 🔥

💜 Reserve → provision → do stuff → release (the full main character arc)

Reserve a particular system, provision it, do some work on it, and then release it. Obsessed with this little lifecycle:

bkr system-reserve system1.example.invalid
bkr system-provision --kernel-opts "nogpt" \
                     --distro-tree 12345 \
                     system1.example.invalid
# do some work on the system
bkr system-release system1.example.invalid

Note the \ line continuation in the bkr system-provision call — that's doing the heavy lifting so --kernel-opts "nogpt", --distro-tree 12345, and the <fqdn> all stay in one command. Copy it exactly, bestie 🍓

🌈 Release more than one system

Because why release one when you can release two? Efficiency queen behaviour:

bkr system-release system1.example.invalid system2.example.invalid

🌟 SEE ALSO 🌟

  • bkr(1) — the parent page, go read it for the common options 💫

👑 AUTHOR 👑

The Beaker team <beaker-devel@lists.fedorahosted.org> — absolute legends, sending them love 🫶

2013-2025 Red Hat, Inc.

Fr fr, the only thing you actually have to remember: give the system back with bkr system-release <fqdn>... and check that exit status like your life depends on it 💅

Okay that's the whole page, bestie — you ate that. This cute lil' rewrite is from version 29.2, dated May 26, 2025, and it's BKR-SYSTEM-RELEASE(1) all the way through 🌸💖🌈

📦 where this page comes from