Bug 1302601

Summary:	Describe directory structure of /var/lib/pulp in Satellite6
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Docs User Guide	Assignee:	satellite-doc-list
Status:	CLOSED DUPLICATE	QA Contact:	satellite-doc-list
Severity:	medium	Docs Contact:
Priority:	high
Version:	Unspecified	CC:	adahms, bbuckingham, dmacpher, ktordeur
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:	2017-05-29 06:27:03 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:

Description Pavel Moravec 2016-01-28 08:55:23 UTC

Description of problem:
For investigating Satellite6 cases relevant to some pulp repository issue, it is important to know / understand directory structure of /var/lib/pulp. Where to find what information / data (repository, updateinfo,..), what symlinks should be there etc.

Lack of this informatino blocked me on investigation of several cases already.

I am happy to contribute to composing such document / KCS article, but need some input.

I understand some data will have to come from pulp team and some from katello as e.g. some directories names contain organization / content view / environment / .. in them.


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


How reproducible:
n.a.


Steps to Reproduce:
n.a.


Actual results:
no doc describing /var/lib/pulp


Expected results:
some doc for that


Additional info:

Comment 3 Andrew Dahms 2016-12-02 00:42:24 UTC

Moving back to the default assignee to be re-triaged as the schedule allows.

Comment 4 Andrew Dahms 2017-05-29 06:27:03 UTC

Hi Pavel,

Thank you for raising this bug.

We are now working on this content in a separate bug where a similar request was raised - BZ#1419606.

I will close this bug as a duplicate, and you are welcome to add questions to that bug or follow up with me if there is any further detail that we can provide.

Kind regards,

Andrew

*** This bug has been marked as a duplicate of bug 1419606 ***