The nova unit tests recently started to fail on systems lacking mkisofs
(like mac osx). Skip these mkisofs calls by patching _make_iso9660.
Change-Id: I350aafa878616f74df506c1bc9ee5f26ea06fe97
Closes-Bug: #1630420
When user tries to create snapshot of instance and at the same time
if another request tries to delete the instance, at that time image
goes in saving status for forever because of race between instance
delete and snapshot requests.
Caught exceptions(InstanceNotFound and UnexpectedDeletingTaskStateError)
in except block and deleting the image which got stuck in saving state.
Closes-Bug: #1555065
Change-Id: If0b918dc951030e6b6ffba147443225e0e4a370a
DevicePathInUse might be raised in attach action,
we didn't catch it so a 500 error might be returned
to end user.
Change-Id: Ic9f0979b5adef28bb47756e7fc2ce5a3d6493298
Closes-Bug: 1621452
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Change-Id: Ibf005a434417c7b6ad7b7bada27d45f3bf238db1
On revert_resize(), the migration context was dropped hence setting it
to None. The problem is that the migration context is needed when
executing finish_revert_resize() so that the neutron port can be updated
with the right binding profile.
This patch moves the instance.drop_migration_context() call out from the
resource tracker so that the migration context can be dropped at the
appropriate times: after RT.drop_move_claim() is called in the compute
manager's confirm_resize() call and after the virt driver's
finish_revert_resize() in the compute manager's finish_revert_resize()
call.
Change-Id: I1b7b2573de4380576dd8b801ed59d8955b0ab72a
Partial-bug: #1512880
These tests did not mock imagebackend and left a temporary instances/
directory after completion. As imagebackend is not really used, just
mock it entirely instead of using a tempdir fixture.
TrivialFix
Change-Id: I5f084112757bedf9a5da546033d3a5fc68e68991
When block live migrate an instance with ephemerals an exception
FlavorDiskSmallerThanImage can be raised because the size used to
create the base ephemeral disk is the total size allowed by flavor
which can be greater than the size effectively requested by the
instance when spwaned.
Closes-Bug: #1628449
Change-Id: I264f5beb73d9b8ba441aec8f8a317b553a7e22c0
Now that the credentials dict is the return from
context.to_policy_values() and not the context object itself there's no
need to attempt to pop the 'auth_token' key out before logging.
Change-Id: I3b4eacf6c7d97a4243aff026aefbb53017d5e840
For resize/cold-migration it's possible that instance
already changed host to destination, but no confirm/revert
has happened yet. In that case resource tracked starts spamming
errors, because it's impossible to match migration and instance.
It's safe to lower log level to debug in that case.
Change-Id: I70cb7426e0e2849ee7d01205ce7b2d883a126d66
Closes-Bug: #1555320
This adds a --until_complete flag to the db archive command, which will
attempt to run batches of max_rows continuously until archiving has
completed (or stops being able to archive anything). We also take care
to catch KeyboardInterrupt so that it will, if stopped, still print
the verbose report at the end. Instead of printing the table on each
iteration, we print some progress information and then provide a completed
summary table at the end of the run.
This also defaults max_rows to a sane value. The previous meaning of not
providing a value was "archive a whole table in a single operation",
which was useful only in the most simple of cases. Now that we have
a more reasonable "do it until you are done" mechanism, we default this
to 1000 rows for sanity, which also serves as the batch size for the
continuous mode.
Implements blueprint archive-deleted-rows-all
Change-Id: I2929c2f5b3116b63a4666b258bf078bc51d4e45a
While debugging a failed event delivery bug, I realized that our
logging of the event path leaves some ambiguity which makes it
difficult to follow. This adds the instance host to the existing
debug message on the API side, which helps to identify that events
are being sent to the right (or wrong) host. Further, which logs
a warning in the case where a compute host receives an instance
message when no thread was waiting for it.
Change-Id: I9a1461493a19750fe5dc11869cfa33d2e6fd3c6f