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:
failed to get info on created scap content: wrong number of arguments (given 1, expected 0)


Version-Release number of selected component (if applicable):
satellite-6.4.0-15.el7sat.noarch


How reproducible:
sometimes


Steps to Reproduce:
1. hammer -v -u admin -p changeme --output=csv scap-content create --scap-file="/tmp/ssg-rhel6-ds.xml" --title="TtCyeKUxlA"
2. hammer -v -u admin -p changeme scap-content info --id="12"


Actual results:
[ERROR 2018-09-23T04:52:47 API] 500 Internal Server Error
[ERROR 2018-09-23T04:52:47 Exception] wrong number of arguments (given 1, expected 0) wrong number of arguments (given 1, expected 0)


Expected results:
Should work

The problem is reproducible when there is a default location/organization set for hammer.

hammer defaults add --param-name location_id --param-value 2
hammer scap-content info --id 12

The error disappears when the default is removed.

*** This bug has been marked as a duplicate of bug 1631340 ***

Thank you Ondřej!