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.
Description of problem:
runninng:
hammer -v -u admin -p changeme --output=csv organization list --help --per-page="10000"
ends with Error: undefined method `[]' for nil:NilClass
Seemingly this is influenced by the position of --output=csv argument, moving it to the end mitigates the issue.
Version-Release number of selected component (if applicable):
Satellite 6.5 snap 2
Good catch Nikhil, they're dupes. I didn't spot it early enough and happened to clone the other issue - I'm sorry for that. I'm going to close this one for a bit more complete description of the other.
Peter, just for you to know: Hammer ignores any parameter that comes after --help or -h. Not best approach but it's a feature of the framework that we use (Clamp). Hence moving --output=csv to the end "mitigates" the issue.
*** This bug has been marked as a duplicate of bug 1649231 ***