Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
There are several places in the katello command-line where the options should be more unified. For instance, to list the distributions, use the repo name by running the following command:
katello -u admin -p admin distribution list --product RHEL --repo 6.2 --org ACME_Corporation
But, to get information on the distribution, you must use the repo ID:
katello -u admin -p admin distribution info --repo_id 1 --id 'ks-Red Hat Enterprise Linux-Server-6.2-x86_64'
Why can we not use --repo in the `distribution info` command? It is odd to require --repo and --repo_id with the same subcommand.
There are many other instances of this same issue in other sub commands.
Thew new hammer cli which is being used in Satellite 6 now implementes this feature as you described. I am marking this as CLOSED/NEXTRELEASE. If you have concerns whth this, please feel free to re-open the bug.