blob stuck in "saving" status.
glare upload results with: INFO - ERROR (app) HTTPConflict (HTTP 409)
When going to glare_artifact_blobs (after more than 12 hours) we can find blob in "saving" status, and NULL values for url, sha1, key_name, sha256.
When Trying to delete the artifact we get 409 (as expected):
{"explanation": "There was a conflict when trying to complete your request.", "code": 409, "error": {"message": "You cannot change artifact status if it has uploading blobs.", "type": "Conflict"}, "title": "Conflict"}
ERROR (app) HTTPConflict (HTTP 409)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/cliff/app.py", line 400, in run_subcommand
result = cmd.run(parsed_args)
File "/usr/lib/python2.7/site-packages/osc_lib/command/command.py", line 41, in run
return super(Command, self).run(parsed_args)
File "/usr/lib/python2.7/site-packages/cliff/command.py", line 137, in run
return_code = self.take_action(parsed_args) or 0
File "/usr/lib/python2.7/site-packages/glareclient/osc/v1/artifacts.py", line 344, in take_action
type_name=parsed_args.type_name)
File "/usr/lib/python2.7/site-packages/glareclient/v1/artifacts.py", line 239, in delete
self.http_client.delete(url)
File "/usr/lib/python2.7/site-packages/glareclient/common/http.py", line 275, in delete
return self.request(url, "DELETE", **kwargs)
File "/usr/lib/python2.7/site-packages/glareclient/common/http.py", line 227, in request
raise exc.from_response(resp)
HTTPConflict: HTTPConflict (HTTP 409)
Traceback (most recent call last):
File "/usr/bin/glare", line 10, in <module>
sys.exit(main())
File "/usr/lib/python2.7/site-packages/glareclient/shell.py", line 336, in main
return GlareShell().run(argv)
File "/usr/lib/python2.7/site-packages/cliff/app.py", line 279, in run
result = self.run_subcommand(remainder)
File "/usr/lib/python2.7/site-packages/cliff/app.py", line 400, in run_subcommand
result = cmd.run(parsed_args)
File "/usr/lib/python2.7/site-packages/osc_lib/command/command.py", line 41, in run
return super(Command, self).run(parsed_args)
File "/usr/lib/python2.7/site-packages/cliff/command.py", line 137, in run
return_code = self.take_action(parsed_args) or 0
File "/usr/lib/python2.7/site-packages/glareclient/osc/v1/artifacts.py", line 344, in take_action
type_name=parsed_args.type_name)
File "/usr/lib/python2.7/site-packages/glareclient/v1/artifacts.py", line 239, in delete
self.http_client.delete(url)
File "/usr/lib/python2.7/site-packages/glareclient/common/http.py", line 275, in delete
return self.request(url, "DELETE", **kwargs)
File "/usr/lib/python2.7/site-packages/glareclient/common/http.py", line 227, in request
raise exc.from_response(resp)
glareclient.exc.HTTPConflict: HTTPConflict (HTTP 409)
Usually the service automatically deletes a blob instance if there was an error during uploading process. For sure we can't guarantee this behavior always, because in some cases mysql db doesn't respond in time.
I agree that we must prevent such situations and allow users to delete blobs with 'saving' status.
But we must do it right and exclude the situations when malicious users will reupload their data, and therefore clog the storage.
My proposal is to add a new policy for deleting blobs with saving status and let only operators perform this action.