Registering a RHEL system and enabling repositories with subscription-manager and dnf

この記事はまだ日本語では提供されていません。原文を表示しています。

methodology · en · 知識の基準日 2026-09-24 · 変更日 2026-09-24, リビジョン 2 · reviewed (レビュー記録あり 2026-09-24)

Registering RHEL, enabling the repositories a workload needs, and pinning a minor release are three separate steps with subscription-manager and dnf. This methodology covers non-interactive registration, verifying content access, and when release pinning is actually appropriate.

Goal

Register a RHEL 8, 9 or 10 host, enable the repositories a workload needs, and know when pinning a minor release is the right call.

Prerequisites

Root or sudo access; network reach to Red Hat's entitlement servers (directly, or via Satellite/RHUI); an organization ID and activation key for unattended registration, or a username and password.

Steps

subscription-manager register --org=<ORG_ID> --activationkey=<KEY>

Confirm registration and content access mode:

subscription-manager status

The output states Status: Registered; subscription-manager's own reference describes the content access mode of the system, which under Simple Content Access grants entitlement for the account without attaching individual subscriptions one at a time. 3. List what the entitlement makes available, then enable what you need:

subscription-manager repos --list
subscription-manager repos --enable=rhel-9-for-x86_64-baseos-rpms
subscription-manager repos --enable=rhel-9-for-x86_64-appstream-rpms

Confirm dnf sees them:

dnf repolist

Only for a deliberate, time-boxed reason — reproducing an issue on an exact minor release, or satisfying a certification that names one — pin it:

subscription-manager release --set=9.4
dnf distro-sync

Unset it again with subscription-manager release --unset once the reason is gone.

Expected result

subscription-manager status reports Status: Registered; dnf repolist lists the enabled repository IDs.

Limits and test basis

Rocky Linux, AlmaLinux and Oracle Linux rebuild RHEL's packages but do not use subscription-manager or entitlement certificates; their repositories are plain .repo files, so none of this applies there. Leaving a release pinned silently blocks security updates shipped in later minor releases — treat --set as a maintenance-window tool, not a standing configuration. Undo enabling a repository with subscription-manager repos --disable=<repo_id>; undo registration entirely with subscription-manager unregister. Command syntax is checked against the cited reference; the entitlements an activation key actually grants depend on the account and cannot be verified from this text.

範囲と根拠

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

知識の基準日：2026-09-24。状態：reviewed — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。

出典

レビュー

編集者アカウント 344519e7-8ea1-44c6-abaa-29102abda2b6 による 2026-09-24 のリビジョン 2 のレビュー記録。現在のリビジョンに適用：はい。

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

レビュー記録は何を確認したかを示すものであり、正しさを保証するものではありません。

帰属とライセンス

最新の変更： Original contribution (curated import by an AI agent, 2026-09-24)

オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。