Bug 1402418

Summary:	cdn-sync output is not that informative as satellite-sync output
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Satellite Synchronization	Assignee:	Gennadii Altukhov <galtukho>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	580	CC:	dyordano, galtukho, jdobes, jdostal, lhellebr, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-backend-2.5.3-160-sat	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-05 13:57:18 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:	1450111

Description Jan Hutař 2016-12-07 13:51:31 UTC

Description of problem:
cdn-sync output is not that informative as satellite-sync output, specifically see below.


Version-Release number of selected component (if applicable):
cdn-sync-mappings-0.0.1-1.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Sync some channel with cdn-sync, compare with satellite-sync


Actual results:
 * output is not clearly divided into sections (pkg download, import,
   errata..., ks...)
 * no ETA shown when downloading packages
 * when running with "--no-rpms", no indication shown that only package
   headers are downloaded
 * no progress bar for:
   * linking packages to channel
   * importing erratas
 * no indication on how many new errata needs to be imported
 * we needlessly print same repo url 3+ times
 * showing exact coms filename is more "verbose" or "debug" level output


Expected results:
Should be as informative as satellite-sync.

Comment 3 Tomas Lestach 2017-08-21 12:36:41 UTC

Ack, please, just extend existing output, do not try to re-design/re-structure the current output.

Comment 4 Gennadii Altukhov 2017-09-25 13:54:08 UTC

the bug is fixed in upstream. spacewalk.git:
687c90e02d9fffad7f5ed9f6facb2d9f9a9201ff

Some of the issues above cannot be resolved due to difficulty in realization. For example:
it cannot show a progress bar for errata importing and package linking because it uses external library call and passes all the packages/errata to it and just wait for completing.

Comment 7 Lukáš Hellebrandt 2018-01-18 13:27:24 UTC

Only points 1, 3 and 5 have been actually fixed. After talking to Gennady, I am assigning this back to him to make a few minor fixes.

Comment 8 Gennadii Altukhov 2018-01-18 15:05:02 UTC

cdn-sync still shows repo URL twice. There is no such bug in upstream, it was fixed in commit spacewalk.git:
5ed678edebce18b623517b5e0e03201f6781a463

We need only one line of this patch, so no need to cherry-pick the entire commit from upstream.

Comment 11 Lukáš Hellebrandt 2018-01-19 11:39:14 UTC

Verified with spacewalk-backend-2.5.3-160.

* output is not clearly divided into sections (pkg download, import,
  errata..., ks...)
 => Fixed
* no ETA shown when downloading packages
 => Hard to fix according to Gennady, would require code change -> Wontfix
* when running with "--no-rpms", no indication shown that only package
  headers are downloaded
 => Fixed
* no progress bar for:
  * linking packages to channel
  * importing erratas
 => Hard to fix according to Gennady, would require code change -> Wontfix
* no indication on how many new errata needs to be imported
 => Fixed
* we needlessly print same repo url 3+ times
 => Fixed
* showing exact coms filename is more "verbose" or "debug" level output
 => We agreed with Gennady we will hide URL but displaying a filename is a good thing and we will keep it

In conclusion, easy to fix items were fixed and hard to fix ones are not worth the effort -> Verified

Comment 14 errata-xmlrpc 2018-02-05 13:57:18 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-2018:0274