when running nova image-create with --poll we continues to report even when instance is desroyed

[Dafna Ron]

I launched an instance and started a nova create-image with --pool
Than I destroyed the instance.
although the qemu pid is gone and so is the image --pool continues to run and report 0% progress:

[root@puma31 ~(keystone_admin)]# nova image-create 9bf5fc48-0b44-497a-bdb2-d3fd6a60582c poll-test1 --poll
Server snapshotting... 25% complete

Server snapshotting... 25% complete
Server snapshotting... 25% complete
Server snapshotting... 0% completee
Server snapshotting... 0% complete
Server snapshotting... 0% complete
Server snapshotting... 0% complete
Server snapshotting... 0% complete

I think that we should exit if qemu pid is gone.

[Ritesh Paiboina (rsritesh)]

The best way is not to allow a user to delete an instance, when the status of the instance is SNAPSHOTTING

Any comments ?

[Shuichiro MAKIGAKI (shuichiro-makigaki)]

I think nova API accepts delete request during taking a snapshot. It also should be restricted by server side.

[Shuichiro MAKIGAKI (shuichiro-makigaki)]

One more comment, we have to decide if snapshoting is given priority over deleting or not.

[David Kranz (david-kranz)]

Yes, this this would be an API change. And not a good one IMO. Users need to be able to delete vms.

[Ritesh Paiboina (rsritesh)]

https://review.openstack.org/#/c/185942/

Code review is in progress.

[Michael Glaser (mikeg451)]

Bug has been open for over 2 years, and it appears it's not longer an issue.

When I test this now I get:

Server snapshotting... 25% completeERROR (NotFound): Image not found. (HTTP 404) (Request-ID: req-0ea31e28-fa8c-45d6-a97e-50a68041cf8e)

and the CLI returns to a prompt.

If anyone thinks this is still an open issue, then please advise.

[Michael Glaser (mikeg451)]

Bug appears to have been resolved.