Bug 1136812 - 'hammer import all' does not trigger repository synchronization
Summary: 'hammer import all' does not trigger repository synchronization
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Transitions
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Grant Gainey
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks: stargate-GA-tracker
TreeView+ depends on / blocked
 
Reported: 2014-09-03 11:19 UTC by Tomas Lestach
Modified: 2014-09-04 09:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-03 12:04:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Lestach 2014-09-03 11:19:59 UTC
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

Comment 2 Grant Gainey 2014-09-03 12:04:15 UTC
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)


Note You need to log in before you can comment on or make changes to this bug.