Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #1537

closed

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

Write documentation on how to debug a lazy setup

Added by jcline@redhat.com over 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
jcline@redhat.com
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
Actions
Copy link
 #1

Updated by mhrivnak over 8 years ago

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

Added by Jeremy Cline about 8 years ago

Revision dc1e0593 | View on GitHub

Add some troubleshooting documentation for lazy.

Actions
Copy link
 #2

Updated by jcline@redhat.com about 8 years ago

  • Status changed from ASSIGNED to POST
Actions
Copy link
 #3

Updated by jcline@redhat.com about 8 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #4

Updated by rbarlow about 8 years ago

  • Version set to Master
  • Platform Release set to 2.8.0
Actions
Copy link
 #5

Updated by dkliban@redhat.com about 8 years ago

  • Status changed from MODIFIED to 5
Actions
Copy link
 #6

Updated by dkliban@redhat.com about 8 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Copy link
 #7

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added
Actions
Send by e-mail Copy link

Also available in: Atom PDF