Output from /var/log/foreman/production.log while getting the above traceback:
===
Processing by Katello::Api::V2::OrganizationsController#index as application/json;version=2
  Parameters: {"per_page"=>"999999", "api_version"=>"v2", "organization"=>{}}
Authorized user admin(Admin User)
  Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.2.0/app/views/katello/api/v2/organizations/index.json.rabl within api/v2/layouts/index_layout (6.5ms)
Completed 200 OK in 53ms (Views: 7.9ms | ActiveRecord: 13.9ms)
===

The code to call the API is this:
===
      # Call API. Ideally accessed via +api_call+ instance method.
      # This is supposed to be the only way to access @api.
      def api_call(resource, action, params = {}, headers = {}, dbg = false)
        @api.resource(resource).call(action, params, headers)
      rescue
        puts("Error on api.resource(#{resource.inspect}).call(#{action.inspect}, #{params.inspect}):")
        raise
      end

===

which is failing like this:
===
Error on api.resource(:organizations).call(:create, {:description=>"Imported 'RED HAT SATELLITE ENGINEERING' organization from Red Hat Satellite 5", :name=>"RED HAT SATELLITE ENGINEERING", :id=>1}):
===

because of this error-return:
===
Caught ApipieBindings::MissingArgumentsError:ApipieBindings::MissingArgumentsError: name
===

As a test, modified the call-code for organization-create specifically to be this:
===
        p = {'organization'=>params}
        @api.resource(resource).call(action, p, headers)
===

and it failed with the same error:
===
Caught ApipieBindings::MissingArgumentsError:ApipieBindings::MissingArgumentsError: name
===

while spitting out the following debug output:
===
Error on api.resource(:organizations).call(:create, {"organization"=>{:description=>"Imported 'RED HAT SATELLITE ENGINEERING' organization from Red Hat Satellite 5", :name=>"RED HAT SATELLITE ENGINEERING", :id=>1}}):
===

and the following production.log statement:
===
Processing by Katello::Api::V2::OrganizationsController#index as application/json;version=2
  Parameters: {"organization"=>{}, "api_version"=>"v2"}
Authorized user admin(Admin User)
  Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.2.0/app/views/katello/api/v2/organizations/index.json.rabl within api/v2/layouts/index_layout (7.1ms)
Completed 200 OK in 50ms (Views: 9.2ms | ActiveRecord: 10.5ms)
===

The cause of this error is a validation of parameters that was added to apipie-bindings recently. It currently checks just required parameters according to apipie docs.

In this case the problem originates in somewhat inconsistent API parameter format in Katello and Foreman. Unfortunately Organization is resource from Foreman that is extended in Katello and it has both nested and not nested parameter format (See https://<your-satellite>/apidoc/v2/organizations/create.html) I believe that Organization PUT/POST is the only resource where the problem is present.

The solution for the issue you are experiencing would be to fix the parameters you are sending to match the API documentation (or fix the API/API documentation). Minimal Org params should look like:

<pre>
{
            "name" => "myOrg",
    "organization" => {
        "name" => "myOrg"
    }
}
</pre>

Created attachment 992298 [details]
hammer_cli_import-0.10.6.gem

jsherrill requested a reproducer, so here's one.

Install the attached gem, hammer_cli_import-0.10.6.gem, in order to get past the problem in BZ#1192581

Put the below into a file, /tmp/users.csv:

===
organization_id,organization,user_id,username,last_name,first_name,position,email,role,creation_time,last_login_time,active
1,RED HAT SATELLITE ENGINEERING,1,admin,Nimda,Admin,,root@localhost,Organization Administrator;Satellite Administrator,2015-01-28 18:38:36,2015-02-11 19:13:25,enabled
===

and then run the following import command:

===
hammer import organization --csv-file /tmp/users.csv --debug --verbose
===

and watch it fail:

===
(1192581) ~/hammer-cli-import $ hammer import organization --csv-file /tmp/exports/users.csv --debug --verbose 
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT
Importing from /tmp/exports/users.csv
Creating new organization: RED HAT SATELLITE ENGINEERING
entity_hash: {:description=>"Imported 'RED HAT SATELLITE ENGINEERING' organization from Red Hat Satellite 5", :name=>"RED HAT SATELLITE ENGINEERING", :id=>1}
Caught ApipieBindings::MissingArgumentsError:ApipieBindings::MissingArgumentsError: name while processing CSV line:
{"organization_id"=>"1", "organization"=>"RED HAT SATELLITE ENGINEERING"}
/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.11/lib/apipie_bindings/action.rb:62:in `validate!'
/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.11/lib/apipie_bindings/api.rb:158:in `call'
/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.11/lib/apipie_bindings/resource.rb:14:in `call'
/usr/lib/ruby/gems/1.8/gems/hammer_cli_import-0.10.6/lib/hammer_cli_import/base.rb:134:in `api_call'
===

Be sad.

@grant if you actually want debug and verbose output, they need to come before the commands, because they're global flags.

so:
hammer -v -d import organization --csv-file /tmp/users.csv

hammer-cli-import recognizes its own --debug and --verbose.  -v/-d control output from the underlying hammer-infrastructure.

Fixing by special-casing org-create-call.

hammer-cli-import.github 59faf5b8cea6405c8d1d7ac07d1e94ce1ad09d49

Modified by hammer-cli-import.github c106fa0a884567922124cba9108c7b88148dea34

rubygem-hammer_cli_import-0.10.9.1
no such version on any compose?! ON_QA?

VERIFIED. rubygem-hammer_cli_import-0.10.6.3-1.el6_6sat

# hammer import organization --verbose --csv-file /tmp/exports/users.csv --upload-manifests-from '/tmp/manifests''
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT
Importing from /tmp/exports/users.csv
Creating new organization: RED HAT SATELLITE ENGINEERING
Uploading manifest /tmp/manifests/RED_HAT_SATELLITE_ENGINEERING.zip to org-id 3
Waiting for the task [4b8d6deb-4594-4913-affb-ef5e30b47bcb] .................
Creating new organization: Organization #2
Uploading manifest /tmp/manifests/Organization__2.zip to org-id 4
Waiting for the task [6f5e9af6-4a48-4f7c-829b-7b83f52f4714] ..........
Creating new organization: Organization #3
Uploading manifest /tmp/manifests/Organization__3.zip to org-id 5
Waiting for the task [3946507d-7ec2-48f4-8924-41d71e3d97d8] ..........
Summary
  Created 3 organizations.
  Uploaded 3 manifests.

This bug is slated to be released with Satellite 6.1.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592