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.
Description of problem:
Version-Release number of selected component (if applicable):
subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.8.33-1
subscription-manager: 1.10.8-1.el7
python-rhsm: 1.10.8-1.el7
How reproducible:
3/3
Steps to Reproduce:
1.Register client to candlepin server
2.now execute 'rhsm-debug system ' command
3.
Actual results:
The command was successfully executed with out any error
[root@amd-pike-05 ~]# rhsm-debug system
[root@amd-pike-05 ~]#
Expected results:
When the command "rhsm-debug system" is executed with out the destination it should either display a 'rhsm-debug' usage error or display the help of the rhsm-debug system
Additional info:
The default destination appears to be /tmp which is fine.
In my opionin, the feedback from running "rhsm-debug system" should be the actual path to the zip file that was created. For example...
Expected results:
[root@jsefler-7 ~]# rhsm-debug system
Successfully created: /tmp/system-debug-20131211-464084.zip
I would also like to see the help description for --destination rephrased to...
Actual:
--destination=DESTINATION
the destination location of the zip file
Expected:
--destination=DIRECTORY
the directory location for the debug zip file;
defaults to /tmp
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.