Project

Profile

Help

Test #4463

Assert that accessing content endpoint does not raise 500 for lazy synced content

Added by bherring over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Platform Release:
Tags:
Sprint:

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

Copied from File Support - Issue #4340: "artifact" field causes serialization to blow up if the content units were lazily syncedCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 63048969 View on GitHub
Added by kersom over 1 year ago

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

History

#1 Updated by bherring over 1 year ago

  • Copied from Issue #4340: "artifact" field causes serialization to blow up if the content units were lazily synced added

#2 Updated by daviddavis over 1 year ago

  • Tags deleted (Pulp 3 RC Blocker)

#3 Updated by kersom over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to kersom

#4 Updated by kersom over 1 year 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)

#5 Updated by kersom over 1 year ago

  • Status changed from ASSIGNED to MODIFIED

#6 Updated by kersom over 1 year ago

  • Status changed from MODIFIED to CLOSED - COMPLETE

#7 Updated by bmbouter over 1 year ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF