Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1255208 - [RFE] "Hammer capsule list" list capsules in the order of capsule names
Summary: [RFE] "Hammer capsule list" list capsules in the order of capsule names
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-20 01:25 UTC by Pradeep Kumar Surisetty
Modified: 2019-09-26 13:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-09 19:08:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pradeep Kumar Surisetty 2015-08-20 01:25:57 UTC
Description of problem:

Presently "Hammer capsule list" list capsules in the order of capsule names (alphanumeric) as shown below. Once we start scaling up capsules, this would be difficult to track. 
If used remove one of the capsule, it would be difficult to track which one is active.  Listing capsules in the order of ID's would  be lot easier to track. 


171 | vmcapsule171.perf.lab.eng.rdu.redhat.com   | https://vmcapsule171.perf.lab.eng.rdu.redhat.com:9090  
174 | vmcapsule172.perf.lab.eng.rdu.redhat.com   | https://vmcapsule172.perf.lab.eng.rdu.redhat.com:9090  
181 | vmcapsule178.perf.lab.eng.rdu.redhat.com   | https://vmcapsule178.perf.lab.eng.rdu.redhat.com:9090  
180 | vmcapsule189.perf.lab.eng.rdu.redhat.com   | https://vmcapsule189.perf.lab.eng.rdu.redhat.com:9090  
177 | vmcapsule190.perf.lab.eng.rdu.redhat.com   | https://vmcapsule190.perf.lab.eng.rdu.redhat.com:9090  
178 | vmcapsule191.perf.lab.eng.rdu.redhat.com   | https://vmcapsule191.perf.lab.eng.rdu.redhat.com:9090  
176 | vmcapsule192.perf.lab.eng.rdu.redhat.com   | https://vmcapsule192.perf.lab.eng.rdu.redhat.com:9090  
179 | vmcapsule193.perf.lab.eng.rdu.redhat.com   | https://vmcapsule193.perf.lab.eng.rdu.redhat.com:9090  
175 | vmcapsule194.perf.lab.eng.rdu.redhat.com   | https://vmcapsule194.perf.lab.eng.rdu.redhat.com:9090  
173 | vmcapsule195.perf.lab.eng.rdu.redhat.com   | https://vmcapsule195.perf.lab.eng.rdu.redhat.com:9090  







Version-Release number of selected component (if applicable):

6.1 GA

How reproducible:



Steps to Reproduce:
1.Create capsules with different names.
2.
3.

Actual results:

Listing capsules in the order of capsule names.
Expected results:

List capsules in the order of capsule ID's

Additional info:

Comment 1 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Bryan Kearney 2016-07-26 15:41:38 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 4 Bryan Kearney 2017-11-09 19:08:26 UTC
hammer capsule list now supports the --order flag which resolves this issue.


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