Bug 1136812

Summary:	'hammer import all' does not trigger repository synchronization
Product:	Red Hat Satellite	Reporter:	Tomas Lestach <tlestach>
Component:	Transitions	Assignee:	Grant Gainey <ggainey>
Status:	CLOSED NOTABUG	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	cperry, ggainey, mkollar
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-03 12:04:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1125243

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)