Bug 1312838

Summary:	[RFE] As a user I'd like to see my sync status from CLI
Product:	Red Hat Satellite	Reporter:	Tomas Strachota <tstrachota>
Component:	Hammer	Assignee:	Tomas Strachota <tstrachota>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	bbuckingham, cwelton, jcallaha, xdmoon
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/13616
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:30:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Strachota 2016-02-29 11:02:46 UTC

The command should display:

* time of last synchronization
* last sync errors
* environments that are out of sync
* progress and status of the current tasks
* content counts per environment and content view

Proposed command: 'hammer proxy content synchronization-status'

Since content counts can be longish and are probably more suitable to be displayed as a list, they could be handled by a separate command: 'hammer proxy content list'

Comment 1 Tomas Strachota 2016-02-29 11:02:48 UTC

Created from redmine issue http://projects.theforeman.org/issues/13616

Comment 2 Tomas Strachota 2016-02-29 11:02:52 UTC

Upstream bug assigned to tstrachota

Comment 4 Bryan Kearney 2016-03-02 23:10:32 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/13616 has been closed
-------------
Anonymous
Applied in changeset commit:hammer-cli-katello|31062ae116efa8ab30ce3b01ea1d758fd417b790.

Comment 6 jcallaha 2016-04-11 20:32:43 UTC

Verified in Satellite 6.2 Beta Snap 6 Compose 1. Sync status now correctly displayed in hammer.

Comment 8 Bryan Kearney 2016-07-27 11:30:12 UTC

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/RHBA-2016:1501