0.7.10 has been released and is compatible with 0.7.x. Instead
of pinning to 0.7.9, simply pin to 0.7.x to avoid SQLAlchemy 0.8
Change-Id: Iea57598698b4faf906e82a2974497221d07f4d16
Updates the exception formatting in vfs/guestfs so that we
properly raise in cases where there is no root or multiple
roots.
Fixes a TypeError that would occur with the previous code.
Fixes LP Bug #1153414.
Change-Id: I28f9cde5a2da466ebb7397176baaf051ccd4192b
This is one change in a series aimed at removing the use of instance-linked
instance_type objects, in favor of the decoupled type data in
system_metadata. See bug 1140119 for more details.
Change-Id: Iebbb0fa0bf306d6a7c8b83594e13a4b99f27c404
This patch prevents rescuing of volume_backed instances, by checking
for it in the API layer and raising an exception if instance on which a
rescue was attempted is volume backed.
Rescue is supposed to just be a way to log into a wayward instance
if something goes wrong with the base image that may have had some data
(logfiles etc.) and make it possible to grab that - block devices are
assumed to be accessible by re-attaching them, and are considered
persistant so no need for rescue there.
Fixes bug: #1067744
blueprint: improve-boot-from-volume
Change-Id: I8a4b1ccff7406837de3086aa413034e8e647b8fa
The conductor service was missing so running nova-all no longer results
in a complete environment.
This patch adds conductor to the binary list and updates the code to
handle the different way in which conductor specifies the topic and
manager.
Fixes bug 1152371
Change-Id: I4862ad66216ab980e8636e9f3cdbabbace6ee73c
In Models by default type of deleted column is Integer, but bm tabels
use Boolean type for deleted columns.This produce bug in postgresql
(type mismatch).
At this moment we are not able to do any db migrations, so there is
only one way to fix this bug. Change type of deleted columns in Models
from Integer to Boolean.
In Havana we will be able to change deleted columns types to type of id
for bm tables and use soft_delete and UC as in rest of nova.
Fixes bug 1140294
Change-Id: Id56c4bbff7048ed5c746dc995380be9ba0a12c39
This is a tiny change in the actual code, but requires a bunch of
silly changes in the tests because we're so inconsistent with our
(ab)use of instance types there. This attempts to help clean that
up locally a bit.
This is one change in a series aimed at removing the use of instance-linked
instance_type objects, in favor of the decoupled type data in
system_metadata. See bug 1140119 for more details.
Change-Id: Ied1a944a7c762129597d18ded61ce1632657f070
This removes a test that attempted to delete the data from the
instance['instance_type'] structure and confirm that the flavor can
still be fetched. Since this data is no longer consulted in that
action (and will be removed altogether soon), this test is removed.
This is one change in a series aimed at removing the use of instance-linked
instance_type objects, in favor of the decoupled type data in
system_metadata. See bug 1140119 for more details.
Change-Id: I3ba56f9419aece5b9269a181264d09b117ecdb81
This is one change in a series aimed at removing the use of instance-linked
instance_type objects, in favor of the decoupled type data in
system_metadata. See bug 1140119 for more details.
Change-Id: I43c9e9b7d560d8803899360bd7142e393b793f3d
Note that some tests were verifying things that can no longer fail, namely
rebuilding instances who use flavors that have since been disabled. These
tests are removed here.
Also, this changes the order of a piece of logic in the resize/migrate
path where before we would have ended up checking the instance type that
we fetched from sys_meta to see if it was disabled (which makes no sense
now). Reversing the check (to see if we're doing a resize or a migrate
before checking the new flavor) eliminates the problem of the stashed
type not having the 'disabled' attribute.
This is one change in a series aimed at removing the use of instance-linked
instance_type objects, in favor of the decoupled type data in
system_metadata. See bug 1140119 for more details.
Change-Id: I214a693e3bb16c0a365eb9b3afe73601beba4a22
This path corrects a issue where is_power_on function can incorrectly match a
node if its name is a substring of another node.
I have also added a test for this.
fixes bug 1152676
Change-Id: Ic3b0b952d53dcd4464098f98879a84684efe22b2
Authored-by: Chris Krelle <nobodycam@gmail.com>
Looks like the introduction of quotes in fix for previous
bug 1012443 was erroneous.
Fixes LP# 1152504
Change-Id: Ic84739e38e3b3567f1617302a33623de03196f85
Fixes instance evacuation problem when --on-shared-storage flag
specified. The problem occurs as the password variable ends up being
accessed before it is assigned. Also adds missing test case.
Fixes bug 1152492
Change-Id: I461c0f7fcf8835028f7529a7860fb330d1759d68
* max_rows must be positive
Provide a better error message of 'nova-manage db archive_deleted_rows
--max_rows=' is negative.
* Requires a max_rows
* No hidden default of 5000
Fix bug 1145609
Fix bug 1151064
Change-Id: I9078ff2700a0329ac4aff68bb434be5f16a5a3f1
RPC is case sensitive, but URL is not, and DB can be. So pull host_name from DB
in HostAPI RPC layer instead of from passed in from URL. This means RPC will
always get the proper capitalization, and case sensitivity is defined in DB layer.
Fix bug 996879
Change-Id: I448dd4ec3aec4af1adf4487f26ea996db572fa3d
The code currently sets access_ip_* in a 2nd DB call after an instance
goes ACTIVE, which means there's a slight race when someone is querying
the API for their instance. It's possible to see the instance ACTIVE but
access_ip_* will be blank.
To fix this, we should set access_ip_* at the same time the instance goes
ACTIVE. This also removes an unnecessary extra DB call.
Fixes bug 1152328
Change-Id: I0fe542d49fbc95f27a24f57f674264f8789bc527
Dirk Mueller