Project

Profile

Help

Issue #1537

Story #1150: As a user, I can lazily fetch repositories

Write documentation on how to debug a lazy setup

Added by jcline@redhat.com almost 6 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
2.8.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

Currently there is no documentation on how to debug a lazy deployment. A lot of things can go wrong, and it would be best if we had a document to point people to when troubleshooting their setups. This guide should cover:

  • Components involved
  • How to debug each component
  • How to track down the faulty component
  • Common problems

Associated revisions

Revision dc1e0593 View on GitHub
Added by Jeremy Cline over 5 years ago

Add some troubleshooting documentation for lazy.

History

#1 Updated by mhrivnak almost 6 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to jcline@redhat.com
  • Triaged changed from No to Yes

#2 Updated by jcline@redhat.com over 5 years ago

  • Status changed from ASSIGNED to POST

#3 Updated by jcline@redhat.com over 5 years ago

  • Status changed from POST to MODIFIED

#4 Updated by rbarlow over 5 years ago

  • Version set to Master
  • Platform Release set to 2.8.0

#5 Updated by dkliban@redhat.com over 5 years ago

  • Status changed from MODIFIED to 5

#6 Updated by dkliban@redhat.com over 5 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE

#7 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF