When the claim is aborted, this information is no longer correct for the
instance, so we clear it to avoid inconsistencies.
Change-Id: I83a5f06adb22c21392d5fc867728181ea4b0454d
Resolves-bug: 1545675
During evacuation a local connector is built. This is the
wrong connector to use for cinder terminate_connection.
In order to fix this, store the initial connector with
the BDM connection_info. Use the stored connector when
we detect that we have this wrong host situation.
This fix does not work for existing attachments
(made prior to this patch) because existing attachments
don't have the connector stashed in the bdm.connection_info.
In cases where the original connector was not saved, leave
the behavior as-is.
Change-Id: I793f2996fc0af1c321a240ad9348dc9bce816030
Partial-Bug: #1522496
We need to catch up ConsoleTypeInvalid in API layer to avoid 500 error
in case we passed invalid console type (> v2.6).
Closes-Bug: #1551104
Change-Id: I8be6dd1efd9057fb582713e0fe9fe0d626832fda
If using the Neutron network API, listing VIFs will return
a 500. This changes that to return a 400, which does not
require a microversion according to our docs:
http://docs.openstack.org/developer/nova/api_microversion_dev.html
A later change will introduce a microversion to implement the
method for the Neutron API.
Change-Id: I27f48b38d64b34277f001fba86b4e64e9ead937c
Related-Bug: #1183436
This patch simply adds the exception text to the logs so that we don't
lose the troubleshooting data. Without this patch, it's much more
difficult to troubleshoot when something goes wrong as the root
exception text is garbled up and lost.
Change-Id: Ib432fddc9b31fb6f906f6828d52098c9dd059aa2
Closes-Bug: 1553319
Change 022802997c fixed evacuate/rebuild
in the cells API so enable the rebuild-related tests we were skipping
before.
Related-Bug: #1445629
Related-Bug: #1445631
Related-Bug: #1552046
Change-Id: I15f867d8c6ff280bc68a6abf8b0da6e970c2bb39
69ec718b62 changed nova to start using
the network mtu value from neutron (if specified and > 0) when
plugging virtual interfaces. This allows us to finally remove the
deprecated 'network_device_mtu' config option from nova (probably in
Newton).
Add a release note to point out that the segment_mtu value in neutron
is now used to set the mtu value during vif plugging in nova.
Change-Id: Iebffb487cc837427b0ede35aea93ec5f9594165f
Related-Bug: #1549408
Both of these options only had one real in tree sensible
option. Deprecate these so they can be removed and turned into
constants in Newton.
This adds a new ``use_neutron`` config option to replace the
network_api_class option.
Change-Id: Ia79269e2bca0468edde830fc82a15b234e1abcbf
There was only one implementation in tree, and this isn't an extension
point or interface we want people plugging out of tree code into.
Change-Id: Ie2cb64a43198e1155f768ceabe50ce8a004a1d41
This allowed creating a differ class loader for defining vendordata
metadata for the metadata server. The default driver loads from a json
file that can be arbitrarily specified, so is still quite flexible.
Change-Id: I0f9866320cd655134281193c50ec170ea20c011a
Previously this let you replace our SQLAlchemy database layer with
your own. This approach is deprecated. Deployments that felt the need
to use the facility are encourage to work with upstream Nova to
address db driver concerns in the main SQLAlchemy code paths.
Change-Id: If195a6bc399c8b1e2bfb0ea5579f2be21d0bc126
We should deprecate the manager classes used for all of our
services. This is not a thing we actually expect or want to support
people replacing. If we want modular plug points at any of these all
the options should be in tree and specified by constants to switch
between.
Change-Id: Id25bd4870c6e2fda08dc0177b7ed61a8a6091838
In compute.api._check_and_transform_bdm() we have a logic to
avoid boot instances with both image-ref and a volume named
as 'vda' is supplied. Currently, we check the bdm's 'source_type',
but infact we should check its' 'destination_type' as this
shows it is a cinder volume.
Change-Id: I1fe2cf7c6655e0e0c61371c6d7379ecfc7071cec
Closes-Bug: #1522329
How to trigger crash dump depends on hypervisors. NMI is not the only way to
implement the feature. This patch modifies description regarding this feature.
Change-Id: I77d10551650776c06ee4b413f1b027abf6620e83