Project

Profile

Help

Test #4125

Test if creating duplicate content results in 400

Added by kersom 11 months ago. Updated 4 months ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Version:
Platform Release:
Tags:
Sprint:

Description

  • Evaluate if we already have similar tests in place.
  • Create duplicate content
  • Assert that an HTTP Bad Request - 400 was raised
  • Assert that an error (e.g. "There is already a file content unit with relativepath 'foo.tar.gz' and artifact '/pulp/api/v3/artifacts/1/'.") is returned

Checklist


Related issues

Related to File Support - Issue #3436: Creating duplicate content results in 500 IntegrityError MODIFIED Actions
Copied to Pulp - Test #4975: Docker - Test if creating duplicate content results in 400 NEW Actions
Copied to Ansible Plugin - Test #4976: Collection - Test if creating duplicate content results in 400 NEW Actions

Associated revisions

Revision 38e035bb View on GitHub
Added by kersom 10 months ago

Add test to create duplicate content units

Add test to create duplicate content units. They have to share the same
`artifact` and `relative_path`.

https://pulp.plan.io/issues/4125
ref: #4125

Revision ce395742 View on GitHub
Added by kersom 9 months ago

Expand duplicate content unit test case

Expand newly added duplicate content unit test case. Add a test case to
confirm that content units using the same artifact, but different
relative_paths can be create without raise an HTTP exception.

https://pulp.plan.io/issues/4125
ref: #4125

Revision 721966a0 View on GitHub
Added by kersom 9 months ago

Add test to create duplicate content units

Add test to create content duplicate content units.

https://pulp.plan.io/issues/4125
#4125

History

#1 Updated by kersom 11 months ago

  • Related to Issue #3436: Creating duplicate content results in 500 IntegrityError added

#2 Updated by kersom 11 months ago

  • Assignee set to kersom

#3 Updated by daviddavis 10 months ago

  • Description updated (diff)

#4 Updated by daviddavis 10 months ago

This needs to be tested against all plugins (not just pulp_file). To reproduce for other plugins, look at their docs for how to create a content unit and send the same request twice. You should receive a nice 400 + error message.

#5 Updated by kersom 10 months ago

  • Checklist item Add pulp_docker added
  • Checklist item Add pulp_rpm added
  • Checklist item Add to plugin template as well added

#6 Updated by kersom 10 months ago

  • Subject changed from Test if creating duplicate content results in 500 to Test if creating duplicate content results in 400

#7 Updated by kersom 10 months ago

  • Status changed from NEW to ASSIGNED

#8 Updated by dalley 10 months ago

@David Would it make sense to add this to the "using plugin" section of the pulpcore functional smash tests instead of for each individual plugin?

#9 Updated by dalley 9 months ago

  • Checklist item Add pulp_file added
  • Checklist item Add pulp_python added
  • Checklist item Add pulp_ansible added

Adding a few to the checklist -- you don't have to worry about the plugins QE isn't responsible for, but it would really help us to still track those plugins on the same issue.

Maybe we should add a new status which means that QE has finished with it, but it still needs the non-productized plugin teams to take a look and port the changes to their own codebases.

#10 Updated by kersom 9 months ago

  • Checklist item Add pulp_rpm set to Done

#11 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

#12 Updated by kersom 4 months ago

  • Copied to Test #4975: Docker - Test if creating duplicate content results in 400 added

#13 Updated by kersom 4 months ago

  • Copied to Test #4976: Collection - Test if creating duplicate content results in 400 added

#14 Updated by kersom 4 months ago

  • Checklist item deleted (Add pulp_docker)
  • Checklist item deleted (Add to plugin template as well)
  • Checklist item deleted (Add pulp_python)
  • Checklist item deleted (Add pulp_ansible)

#15 Updated by kersom 4 months ago

  • Status changed from ASSIGNED to CLOSED - COMPLETE

Please register to edit this issue

Also available in: Atom PDF