# Subscription-manager installation via Cockpit attempts to activate RedHat subscription

**URL:** <https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [January 22, 2026, 3:59am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157 "2026-01-22T03:59:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JDB](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/jdb/32/3985_2.png) [@JDB](https://forums.rockylinux.org/u/JDB)\
**Post date:** [January 22, 2026, 3:59am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157/1 "2026-01-22T03:59:28Z")

</div>

If you connect to your Rocky 9 system via the Cockpit web interface, there is an option under the Applications tab to install “ **Subscription Manager in Cockpit** ”. If you do this, it might make your system think that it needs to be registered with a RedHat subscription. After that, dnf updates may fail with the following error:

```auto
Unable to read consumer identity

This system is not registered with an entitlement server. You can use subscription-manager to register.

```

Of course, you don’t need a subscription to run Rocky 9. It seems like a bug that Cockpit assumes that you need a subscription. To un-do this screw-up, edit the following file and change “ **enabled=1** ” to “ **enabled=0** ”:

`/etc/dnf/plugins/subscription-manager.conf`

Reboot after? Maybe. To prevent it from happening again, enter the following configuration change:

> subscription-manager config --rhsm.auto\_enable\_yum\_plugins=0

Also, REMOVE subscription-manager from your Cockpit application plugins.

This may answer several previous questions that have already been closed due to inactivity.

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [January 22, 2026, 5:28am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157/2 "2026-01-22T05:28:06Z")

</div>

When installing the subscription manager cockpit plugin, I see this as expected:

![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/b/b618bf0e3be518545eec6a68a0cc3cca0be5a267.png)

Including the subscriptions page after installation.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/8/8e47275b05b16dcc9577027195c1e2275d3bbeb3.png)

Installing this brings in subscription-manager and subscription-manager-cockpit, the latter being needed to interact with the former.

However, installing subscription-manager has it disabled by default.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/6/60f501520186c65daddb0a6b22d7f663a6a7f585.png)

The behavior you’re describing is not typical so I’m curious as to the configuration of this system and the versions of packages it is running, as we patch subscription-manager to be disabled by default.

---

<div class="post-metadata">

**Author:** ![JDB](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/jdb/32/3985_2.png) [@JDB](https://forums.rockylinux.org/u/JDB)\
**Post date:** [January 22, 2026, 6:22am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157/3 "2026-01-22T06:22:41Z")

</div>

Thank you for your reply.

My versions are the same as yours.

I wonder what your **subscription-manager config** contains.

Here is mine. Note that I have set **auto\_enable\_yum\_plugins = 0** , which prevents the problem from occurring. If the value is inside square brackets, then it’s the default. Note that mine is NOT, meaning I set the value myself.

root@JB-Rocky9 [~]

```auto
# subscription-manager config
[server]
   hostname = [subscription.rhsm.redhat.com]
   insecure = [0]
   no_proxy = []
   port = [443]
   prefix = [/subscription]
   proxy_hostname = []
   proxy_password = []
   proxy_port = []
   proxy_scheme = [http]
   proxy_user = []
   server_timeout = [180]

[rhsm]
   auto_enable_yum_plugins = 0
   baseurl = [https://cdn.redhat.com]
   ca_cert_dir = [/etc/rhsm/ca/]
   consumercertdir = [/etc/pki/consumer]
   entitlementcertdir = [/etc/pki/entitlement]
   full_refresh_on_yum = [0]
   inotify = [1]
   manage_repos = [1]
   package_profile_on_trans = [0]
   pluginconfdir = [/etc/rhsm/pluginconf.d]
   plugindir = [/usr/share/rhsm-plugins]
   productcertdir = [/etc/pki/product]
   progress_messages = [1]
   repo_ca_cert = /etc/rhsm/ca/redhat-uep.pem
   repomd_gpg_url = []
   report_package_profile = [1]

[rhsmcertd]
   auto_registration = [0]
   auto_registration_identity_interval = [10]
   auto_registration_interval = [1]
   autoattachinterval = [1440]
   certcheckinterval = [240]
   disable = [0]
   splay = [1]

[logging]
   default_log_level = [INFO]

[] - Default value in use

```

I am sorry that I could not tell you what the value was prior to me ignorantly clicking on the subscription-manager “install” button in Cockpit. Nevertheless, there are a lot of “rhsm” (RedHat) links in the config file, and perhaps the ported subscription-manager in the appstream should nullify those, as well as make sure that the auto\_enable\_yum\_plugins is set to 0.

If my config file is an anomaly, then something strange crawled into my system without my awareness.

---

<div class="post-metadata">

**Author:** ![JDB](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/jdb/32/3985_2.png) [@JDB](https://forums.rockylinux.org/u/JDB)\
**Post date:** [January 22, 2026, 7:16am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157/4 "2026-01-22T07:16:28Z")

</div>

Something strange – I browsed two prior backups, and subscription-manager did not exist on either one. ie, the directory **/etc/rhsm** did not exist, but it does now. (note - that directory contains the configuration file for subscription-manager.) Thus I assume that it was created after clicking the subscription-manager install button in Cockpit. Therefore, I think it might be safe to simply uninstall subscription manager and never touch the Install button in Cockpit again.

```auto
# dnf erase subscription-manager
Dependencies resolved.
======================================================================================================================================
 Package Architecture Version Repository Size
======================================================================================================================================
Removing:
 subscription-manager x86_64 1.29.47.1-1.el9_7.rocky.0.1 @baseos 3.4 M
Removing dependent packages:
 subscription-manager-cockpit noarch 6-2.el9.rocky.0.1 @baseos 1.2 M

Transaction Summary
======================================================================================================================================
Remove 2 Packages

Freed space: 4.6 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing : 1/1
  Erasing : subscription-manager-cockpit-6-2.el9.rocky.0.1.noarch 1/2
  Running scriptlet: subscription-manager-1.29.47.1-1.el9_7.rocky.0.1.x86_64 2/2
Removed "/etc/systemd/system/multi-user.target.wants/rhsmcertd.service".

  Erasing : subscription-manager-1.29.47.1-1.el9_7.rocky.0.1.x86_64 2/2
warning: /etc/rhsm/rhsm.conf saved as /etc/rhsm/rhsm.conf.rpmsave
warning: /etc/dnf/plugins/subscription-manager.conf saved as /etc/dnf/plugins/subscription-manager.conf.rpmsave

  Running scriptlet: subscription-manager-1.29.47.1-1.el9_7.rocky.0.1.x86_64 2/2
  Verifying : subscription-manager-1.29.47.1-1.el9_7.rocky.0.1.x86_64 1/2
  Verifying : subscription-manager-cockpit-6-2.el9.rocky.0.1.noarch 2/2

Removed:
  subscription-manager-1.29.47.1-1.el9_7.rocky.0.1.x86_64 subscription-manager-cockpit-6-2.el9.rocky.0.1.noarch

Complete!

```

Now the config file simply exists as /etc/rhsm/rhsm.conf.rpmsave, which is the vestigial remains of its once-active existence.

If this causes any issues I will post again. 🤯

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [January 22, 2026, 10:10am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157/5 "2026-01-22T10:10:17Z")

</div>

> [@JDB](#):
>
> Now the config file simply exists as /etc/rhsm/rhsm.conf.rpmsave, which is the vestigial remains of its once-active existence.

Not of mere existence, but to retain the “custom edits” you did to `/etc/rhsm/rhsm.conf`

* * *

`dnf provides /etc/rhsm/rhsm.conf` should list the package(s) that _owns_ that file.

`dnf history list subscription-manager` does tell when (in which transactions) you got/updated/removed that package.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [March 23, 2026, 10:11am UTC](https://forums.rockylinux.org/t/subscription-manager-installation-via-cockpit-attempts-to-activate-redhat-subscription/20157/6 "2026-03-23T10:11:11Z")

</div>

Closed on March 23, 2026, 10:11am UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
