Bug 799203

Summary:	Ensure sync log is available while sync operation is still in progress
Product:	[Community] PulpDist	Reporter:	Nick Coghlan <ncoghlan>
Component:	Web App	Assignee:	Nick Coghlan <ncoghlan>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified
Target Milestone:	0.2.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-29 03:04:31 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 Nick Coghlan 2012-03-02 06:21:47 UTC

If a sync job runs into trouble (or is just taking a long time), the sync log is the most useful piece of information for figuring out what is wrong.

The current implementation keeps it hidden until after the sync job is complete - that is unusable in practice.

Comment 1 Nick Coghlan 2012-03-26 06:34:22 UTC

PulpDist 0.0.7 saves in-progress sync logs to /var/www/pub/pulpdist_sync_logs, where they can be easily made available via httpd. This is adequate for 0.1.0.

For 0.2.0, this will be updated to use the sync_progress() importer API call to make the information available via the Pulp REST API rather than a published directory on the web server.

Comment 2 Nick Coghlan 2012-03-28 06:49:54 UTC

*** Bug 805794 has been marked as a duplicate of this bug. ***

Comment 3 Nick Coghlan 2012-03-28 07:08:49 UTC

It turns out there are problems with the concept of storing the sync logs directly in the Pulp database. For large trees, this logs can be on the order of 20 MB or more - they belong on the filesystem, not in a database (NoSQL or otherwise). Having them directly in the sync history induces storage failures in MongoDB, and even if that wasn't the case, the presence of such large chunks of data is a big performance hit for affected REST API operations.

For the moment, the sync_log attributes are simply being removed from the metadata and replaced by a mechanism in the client that uses webbrowser.open_new_tab() to access the sync logs.

This bug will remain open until a more robust and flexible solution is devised.

Comment 4 Nick Coghlan 2016-09-29 03:04:31 UTC

Marking all remaining PulpDist issues as CLOSED-EOL

It doesn't make sense to leave these issues open, as PulpDist hasn't been in active development for quite some time, and restarting development would involve a significant modernisation effort that would likely render many of these requests irrelevant.