Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Use case:
Leapp (RHEL in-place upgrades) is frequently using RHSM to get various info about subscriptions and repositories. In order to limit number of RHSM calls and avoid parsing the test output, it would be nice to have a one place our tool could call, to get the info in machine consumable format.
E.g.
# subcription-manager summary --json
{
"list": [
1,
2,
3
],
"repos": [
1,
2,
3
],
"is_sca": true,
"release": "8.2",
“purpose”: “...”,
...
}
Hi Michal ,
Can you please let us know what are the subscription manager commands that leapp tool is currently using ? We would also like to know does the leapp tool preserve the consumer details after the upgrades ?
thanks,
Rehana
Hi Rehana,
here is the list of rhsm commands we are actually using:
----- (to get some data)
# subscription-manager list --consumed
# subscription-manager status
# subscription-manager repos --list-enabled
# subscription-manager release
----- (to "configure" system as needed)
# subscription-manager refresh
# subscription-manager release --unset
# subscription-manager release --set ...
# subscription-manager repos --enable ....
----------------
I guess you asked just about the first set of commands, which we use to get the data about system.
From that commands we get right now this info:
- The release the subscription-manager is set to
- SKUs the system is attached to
- Repositories that are available to the current system through the subscription-manager
- Repositories that are enabled on the current system through the subscription-manager
- Whether the SCA is used or not
And separately out-of rhsm utility, we get info about the installed product certificate(s).
I am not sure what exactly are you asking about the preservation of consumer details. Can you elaborate on that a little bit? I will try to answer, that expactation is that the upgraded system is still subscribe and user can use it. If this is what you are asking about.
Comment 5RHEL Program Management
2023-08-31 07:28:26 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Use case: Leapp (RHEL in-place upgrades) is frequently using RHSM to get various info about subscriptions and repositories. In order to limit number of RHSM calls and avoid parsing the test output, it would be nice to have a one place our tool could call, to get the info in machine consumable format. E.g. # subcription-manager summary --json { "list": [ 1, 2, 3 ], "repos": [ 1, 2, 3 ], "is_sca": true, "release": "8.2", “purpose”: “...”, ... }