Actions
Test #4463
closed
Assert that accessing content endpoint does not raise 500 for lazy synced content
Platform Release:
Tags:
Sprint:
Quarter:
Description
Steps:
1 - Lazy sync content - using on_demand or streamed.
2 - Access the content endpoint - http GET :8000/pulp/api/v3/content/file/files/
3 - No HTTP exception should be raised.
Related issues
Updated by bherring about 5 years ago
- Copied from Issue #4340: "artifact" field causes serialization to blow up if the content units were lazily synced added
Updated by kersom about 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to kersom
Updated by kersom about 5 years ago
- Subject changed from "artifact" field causes serialization to blow up if the content units were lazily synced to Assert that accessing content endpoint does not raise 500 for lazy synced content
- Description updated (diff)
Added by kersom about 5 years ago
Updated by kersom about 5 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset 6304896991060c06d219f3bcad5700b01fb1b31a.
Updated by kersom about 5 years ago
- Status changed from MODIFIED to CLOSED - COMPLETE
Actions
.
Add test lazy synced content can be accessed via content endpoint
Add test case to verify that lazy synced content can be accessed using the content endpoint without raise an HTTP exception.
https://pulp.plan.io/issues/4463 closes: #4463