Bug 2221661 - [RFE] dnf plugin subscription-manager should mention rhc, when it is available
Summary: [RFE] dnf plugin subscription-manager should mention rhc, when it is available
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: subscription-manager
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: CSI Client Tools Bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-10 14:47 UTC by Jiri Hnidek
Modified: 2023-07-18 09:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-161869 0 None None None 2023-07-10 14:49:24 UTC

Description Jiri Hnidek 2023-07-10 14:47:02 UTC
Description of problem:
When system is not registered, then DNF plugin subscription-manager print warning with suggestion to use subscription-manager for registration. When "rhc" is installed, then this tool should be also suggested as optional CLI tool for registration.

Version-Release number of selected component (if applicable):
[root@rhel9 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 4.2.15-1
subscription management rules: 5.43
subscription-manager: 1.29.33.1-1.el9_2

How reproducible:
100%

Steps to Reproduce:
1. Try to run dnf command on not registered system, where "rhc" is also installed:

[root@rhel9 ~]# dnf install zsh

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


Expected results:

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


Additional info:
When "rhc" is not install, then message should be still the same.


Note You need to log in before you can comment on or make changes to this bug.