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
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