Creating works with files attached in Sirenia generates ObjectNotFoundError message

[rjkati]

Descriptive summary

When creating works in Sirenia which have files attached, I receive an ObjectNotFoundError message on save. I do not receive this message if I deposit a work without a file.

Steps to reproduce the behavior in User Interface (UI)

1. Log into a local build running Sirenia
2. Navigate to Dashboard -> Works -> Add New Work
3. Select a work type. It does not seem to matter which you choose.
4. Fill out the required fields and add a file
5. Check the Deposit Agreement and click Save
6. Observe error message.

Note that if you reload the page after seeing the error message, the work and files will display. If you selected a visibility other than Private in Step 4 or 5, only the work will reflect the selected visibility and the files will be private which may be related to #6863

If you follow the steps above but do not add a file, the error message will not display.

Actual behavior (include screenshots if available)

Saving a new work with a file attached generates an ObjectNotFoundError.

Acceptance Criteria/Expected Behavior

Saving a new work with a file attached should not generate an error and the work and fileset should be available with the selected visibility settings.

Related work

#6863

[rjkati]

This issue does not occur on dev.nurax or pg.nurax

[rjkati]

This works while running the hyrax-fedora-fix branch locally. I can deposit both a PDF and image work without seeing an error message and derivatives generate as expected.