RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1717147 - System Type on "subscription-manager list --consumed" report
Summary: System Type on "subscription-manager list --consumed" report
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: subscription-manager
Version: 8.0
Hardware: All
OS: All
medium
medium
Target Milestone: rc
: 8.1
Assignee: candlepin-bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks: 1724712
TreeView+ depends on / blocked
 
Reported: 2019-06-04 19:53 UTC by Waldirio M Pinheiro
Modified: 2020-05-04 13:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1724712 (view as bug list)
Environment:
Last Closed: 2020-05-04 13:15:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin subscription-manager pull 2111 0 'None' closed Updated from System Type to Entitlement Type 2021-02-16 20:59:22 UTC

Description Waldirio M Pinheiro 2019-06-04 19:53:50 UTC 
Description of problem:
The customer sent a request saying, the machine is a vitual one, however, they still seeing on "System Type" the info "Physical".

Version-Release number of selected component (if applicable):
subscription-manager-1.21.10-3.el7_6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Register the machine on the CDN/RHSM
2. Type the command "subscription-manager list --consumed"
3.

Actual results:
Some information including "System Type: Physical"

Expected results:
Once the machine is virtual, the customer was expecting to see something like this "System Type: Physical"

Additional info:
Comment 2 Waldirio M Pinheiro 2019-06-04 19:59:28 UTC 
Hello all

Let's check the information below

---
[root@sat64 ~]# subscription-manager list --consumed
+-------------------------------------------+
   Consumed Subscriptions
+-------------------------------------------+
Subscription Name:   Red Hat Satellite Employee Subscription
Provides:            Red Hat Beta
                     Red Hat Satellite
                     Red Hat Satellite with Embedded Oracle
                     Red Hat Satellite 5 Managed DB
                     Red Hat Satellite Proxy
                     Red Hat Satellite - Extended Life Cycle Support
                     Red Hat Satellite 5 Managed DB - Extended Life Cycle Support
                     Red Hat Satellite Proxy - Extended Life Cycle Support
                     Red Hat Software Collections (for RHEL Server)
                     Red Hat Satellite 6 Beta
                     Red Hat Satellite Capsule
                     Red Hat Software Collections Beta (for RHEL Server)
                     Red Hat Enterprise Linux High Availability for x86_64
                     Red Hat Ansible Engine
                     Red Hat Enterprise Linux Load Balancer (for RHEL Server)
                     Red Hat Enterprise Linux Server
SKU:                 SER0232US
Contract:            11083281
Account:             540XXX
Serial:              567225507XXXXXXXX
Pool ID:             8a85f98156fed8130XXXXXXXX
Provides Management: Yes
Active:              True
Quantity Used:       1
Service Level:       Self-Support
Service Type:        L1-L3
Status Details:      Subscription is current
Subscription Type:   Standard
Starts:              09/02/2016
Ends:                12/31/2021
System Type:         Physical
---


We can see "System Type: Physical" what suggest this machine to be a Physical machine, however, continuing the debug we can confirm this is a virtual one
---
# subscription-manager facts | grep virt
lscpu.virtualization_type: full
proc_cpuinfo.common.address_sizes: 40 bits physical, 48 bits virtual
virt.host_type: kvm
virt.is_guest: True
virt.uuid: 1358737A-2093-4D6F-B806-C564695AFBC1
---

After check internally (Thanks crag), we can see the "System Type" information is related to the entitlement, on the case above "SER0232US". That said, this should not be "System Type", instead, should be something like "Entitlement Type". To complement, the information about "System Type" should be valid BUT presenting the correct information related to the local machine.

Thank you.



Best Regards
-- 
Waldirio M Pinheiro | Senior Software Maintenance Engineer
Comment 3 Chris Snyder 2019-06-06 15:53:50 UTC 
Rich,

What are your thoughts on changing the phrasing of "System Type" on subscriptions which have been consumed to "Entitlement Type"?
Comment 4 Rich Jerrido 2019-06-06 16:35:02 UTC 
(In reply to Chris Snyder from comment #3)
> Rich,
> 
> What are your thoughts on changing the phrasing of "System Type" on
> subscriptions which have been consumed to "Entitlement Type"?

I support this. 

'System Type' implies (to the casual user) a system fact (i.e. This system is physical or virtual). 

'Entitlement Type' states more cleanly what type of 'thing' you are attaching. (And since you can attach a physical entitlement to a virtual system in many instances, this distinction should be clarified)
Comment 5 John Sefler 2019-06-26 22:17:45 UTC 
Testing Version....
[root@rhsm-auto8-client2 ~]# rpm -q subscription-manager
subscription-manager-1.25.11-1.el8.x86_64

[root@rhsm-auto8-client2 ~]# subscription-manager register --auto-attach
<-- snip -->
[root@rhsm-auto8-client2 ~]# subscription-manager list --available | egrep "(Entitlement|System) Type:" 
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Virtual
Entitlement Type:    Physical
Entitlement Type:    Virtual
Entitlement Type:    Virtual
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Physical
Entitlement Type:    Virtual
Entitlement Type:    Physical
[root@rhsm-auto8-client2 ~]# 
[root@rhsm-auto8-client2 ~]# subscription-manager list --consumed | egrep "Type: *(Physical|Virtual)"
System Type:         Virtual
[root@rhsm-auto8-client2 ~]# 

The intention in comment 0 and comment 4 was to change the label in "subscription-manager list --consumed", but instead the label was actually changed in the "subscription-manager list --available".

In my opinion, both reports for --available and --consumed should be consistent and report the new label "Entitlement Type".  But if you disagree, then the labeling is currently backwards.

Moving this bug back to NEW/FailedQA
Note You need to log in before you can comment on or make changes to this bug.