Bug 1277501

Summary: Improve messaging for hammer import
Product: Red Hat Satellite Reporter: David O'Brien <daobrien>
Component: TransitionsAssignee: Adam Price <adprice>
Status: CLOSED WONTFIX QA Contact: Lukas Pramuk <lpramuk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1.3CC: bbuckingham, bkearney, dhlavacd, tomckay, tstrachota
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/12379
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-05 15:12:35 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:

Description David O'Brien 2015-11-03 13:28:43 UTC
Description of problem:

The standard output from "hammer import repositories" is vague. For a successful import and sync the only output (unless you use -v) is "Summary: No action taken."

Version-Release number of selected component (if applicable):


How reproducible:

Always?

Steps to Reproduce:
1. Take a 5.7 export and extract as per user doc
2. Import orgs, etc., as described in the doc
3. Run "hammer import repositories" as described in the doc:

# hammer import repository --synchronize --wait --no-async \
> --csv-file /tmp/exports/repositories.csv
[Foreman] Username: admin
[Foreman] Password for admin: 

<several hours later>

Summary
  No action taken.


Actual results:

The import was successful, as evidenced by hammer organization list and hammer product list, but the message doesn't indicate that.

Expected results:

Something along the lines of "All repositories imported and synchronized successfully."

Additional info:

Comment 1 David O'Brien 2015-11-03 13:44:56 UTC
This command could be further improved by adding a progress meter of some sort. The sync can take a LONG time and some people could assume it's in error of some sort and cancel the op.

Comment 2 Bryan Kearney 2015-11-03 14:53:32 UTC
Created redmine issue http://projects.theforeman.org/issues/12379 from this bug

Comment 4 Bryan Kearney 2016-04-11 16:06:13 UTC
Upstream bug component is Uncategorized

Comment 5 David O'Brien 2016-04-18 00:47:37 UTC
Reset docs contact <> daobrien

Comment 6 Bryan Kearney 2016-07-08 20:48:20 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 8 Bryan Kearney 2016-12-16 19:07:04 UTC
Upstream bug component is Hammer

Comment 9 Bryan Kearney 2017-01-05 15:12:35 UTC
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.