-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
media files not being removed from alps after batch ingest #4
Comments
@jenyoung is this occurring on staging anywhere? |
can we look into this early next week please? |
I'm looking. |
mbklein [11:32 AM] [11:33] [11:33] mbklein [11:39 AM] [11:41] Per conversation above, I'll kick off a new issue to run the matterhorn clean out script. |
my test: i tested batch ingesting one audio file. the ingest was successful but the audio file is still sitting in the Alps folder (jen_test). the file has not been removed. it was ingested on friday 12/16. |
@mbklein apart from the cleanup script, it appears master files are still remaining. will you continue to look into this today please. |
@d-venckus @Toputnal User
Also, when I try to
The permissions look normal when I |
fixed @mbklein . T'was ye olde sticky bit which bit us! |
@mbklein should we test once more? @Nic4Images and @jenyoung want to try running another test? |
I'll do a manual move using the avalon account, and then we can try an automated one. |
OK, that's done. 😄 @Nic4Images @jenyoung feel free to try another. |
Jen and I are on it. Update to come after 11AM! |
@mbklein tested a video and audio file batch. went in and were removed from the dropbox as expected. |
Severity
Is the production site running?
Are staff blocked from performing their work?
Descriptive summary
After a successful batch ingest, media files are not being automatically removed from the folder on alps.
Expected behavior
Media files removed from folder upon successful batch ingest.
Actual behavior
Media files remain in alps folder after successful batch ingest
Folders with this issue:
The text was updated successfully, but these errors were encountered: