Actions
Issue #1537
closedStory #1150: As a user, I can lazily fetch repositories
Write documentation on how to debug a lazy setup
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
Updated by mhrivnak almost 9 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jcline@redhat.com
- Triaged changed from No to Yes
Added by Jeremy Cline almost 9 years ago
Updated by jcline@redhat.com almost 9 years ago
- Status changed from ASSIGNED to POST
Updated by jcline@redhat.com almost 9 years ago
- Status changed from POST to MODIFIED
Updated by rbarlow almost 9 years ago
- Version set to Master
- Platform Release set to 2.8.0
Updated by dkliban@redhat.com almost 9 years ago
- Status changed from MODIFIED to 5
Updated by dkliban@redhat.com over 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Add some troubleshooting documentation for lazy.