Skip to content
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.

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

[WIP] spec: Avoid DNF warnings on traditional Fedora hosts and DNF on atomics #3509

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

debarshiray
Copy link
Contributor

It will be good to make it easier to have gratis, self-supported Red Hat Enterprise Linux OCI containers on Fedora Silverblue and Workstation through the RHEL Developer Suite subscription. This includes Toolbx containers created with:

  $ toolbox create --distro rhel --release 9.5

However, when subscription-manager was installed on a Fedora host with DNF4, the subscription-manager DNF plugin printed some spurious warning messages that users didn't like because it made them think that something is wrong. eg., when the host is unregistered:

  $ sudo dnf update
  Updating Subscription Management repositories.
  Unable to read consumer identity

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

  Last metadata expiration check: ...

Or, when the host has been registered:

  $ sudo dnf update
  Updating Subscription Management repositories.

  This system is registered with an entitlement server, but is not
      receiving updates. You can use subscription-manager to assign
      subscriptions.

  Last metadata expiration check: ...

These warnings have no relevance in Fedora, because the purpose of using subscription-manager(8) on a Fedora host is to access RHEL content in OCI containers. There is no need for RHEL content on the Fedora host itself.

Note that these warnings aren't visible on Fedora hosts with DNF5 because the subscription-manager plugin doesn't work with it.

Secondly, until now, subscription-manager had %{_bindir}/dnf-3 and %{_bindir}/dnf4 in its dependency chain. This meant that installing subscription-manager on Fedora Silverblue pulled them in, even though those executables shouldn't be present on Silverblue because they don't work there.

Both these problems can be addressed by disabling the DNF and libdnf plugins on Fedora.

https://bugzilla.redhat.com/show_bug.cgi?id=2246833
https://bugzilla.redhat.com/show_bug.cgi?id=2262228

It will be good to make it easier to have gratis, self-supported Red Hat
Enterprise Linux OCI containers on Fedora Silverblue and Workstation
through the RHEL Developer Suite subscription [1].  This includes Toolbx
containers created with:
  $ toolbox create --distro rhel --release 9.5

However, when subscription-manager was installed on a Fedora host with
DNF4, the subscription-manager DNF plugin printed some spurious warning
messages that users didn't like because it made them think that
something is wrong.  eg., when the host is unregistered:
  $ sudo dnf update
  Updating Subscription Management repositories.
  Unable to read consumer identity

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

  Last metadata expiration check: ...

Or, when the host has been registered:
  $ sudo dnf update
  Updating Subscription Management repositories.

  This system is registered with an entitlement server, but is not
      receiving updates. You can use subscription-manager to assign
      subscriptions.

  Last metadata expiration check: ...

These warnings have no relevance in Fedora, because the purpose of using
subscription-manager(8) on a Fedora host is to access RHEL content in
OCI containers.  There is no need for RHEL content on the Fedora host
itself.

Note that these warnings aren't visible on Fedora hosts with DNF5
because the subscription-manager plugin doesn't work with it.

Secondly, until now, subscription-manager had %{_bindir}/dnf-3 and
%{_bindir}/dnf4 in its dependency chain.  This meant that installing
subscription-manager on Fedora Silverblue pulled them in, even though
those executables shouldn't be present on Silverblue because they don't
work there.

Both these problems can be addressed by disabling the DNF and libdnf
plugins on Fedora.

[1] https://developers.redhat.com/blog/2016/03/31/no-cost-rhel-developer-subscription-now-available

https://bugzilla.redhat.com/show_bug.cgi?id=2246833
https://bugzilla.redhat.com/show_bug.cgi?id=2262228
@debarshiray debarshiray marked this pull request as draft February 14, 2025 14:47
@debarshiray debarshiray changed the title spec: Avoid DNF warnings on traditional Fedora hosts and DNF on atomics [WIP] spec: Avoid DNF warnings on traditional Fedora hosts and DNF on atomics Feb 14, 2025
@debarshiray
Copy link
Contributor Author

Here is an initial scratch build for Fedora 41:
https://koji.fedoraproject.org/koji/taskinfo?taskID=129215936

It seems to work. I am now trying to ensure that libdnf-plugin-subscription-manager isn't left behind after updating subscription-manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant