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:
'hammer import all' tries to do everything automatically (default --directory set to /tmp/exports), so the user does not have to think about any options.
But it does not trigger repository synchronization.

Actual results:

So, the user may run 'hammer import all' several times, but it never imports all the entities, as the repository synchronization isn't triggered. Subsequently, no content-views, activation-keys or content-hosts will be transitioned.

Expected results:
hammer import all shall trigger repo synchronization (at least in the background)

Version-Release number of selected component (if applicable):
rubygem-hammer_cli_import-0.10.2-1.2.el6sat.noarch

How reproducible:
always

Synchronization is left under customer control.  You need to specify --synchronize to trigger it (and probably want to use --wait --no-async as well, the first time, to make sure everything complees before moving to the next step)