This commit removes the direct call to discovery in the tox py34 job.
This was added as a temporary step to enable importing of everything
and is now include by standard in the use of ostestr. There isn't any
reason to keep it around anymore.
Change-Id: I117fbc2108b285aa148cb447c1c01145c43031dd
VIR_MIGRATE_TUNNELLEDVIR_MIGRATE_NON_SHARED_INC is not a valid flag.
Note - fixing this doesn't actually affect the test because we don't
parse the value in init_host(), we just check whether it contains the
VIR_MIGRATE_NON_SHARED_INC string.
Change-Id: If33c63c0c7a3397c2b80714049b509c5918bfdc2
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
The NovaException class only takes the message and kwargs,
so we can't pass substitution variables into the __init__, else
we get a TypeError.
This was apparently untested so a unit test is added for
covering the error case.
Change-Id: If5090f30be8985c4a8e99139dc5be8bf93ce1d12
Partial-Bug: #1530847
For some reason, this entry was added to the should-be-set-in-stone
Liberty release section of the RPC change log.
Change-Id: Iae889ceac957ef26de847fe0bbc427124c1c9bf2
In Nova, we are moving away from using an unnamed dictionary
to represent Glance image metadata. This change alters the
signature_utils module to take in the specific image properties
as individual parameters instead of as a dictionary.
Change-Id: Ia79c847de6ef55ddb1305f24fca47dfb822ad7c8
There are a couple of policy checks where mocks are used to allow the
checks to complete. The mocks aren't referenced later. However they
are listed in the wrong order. While this doesn't impact this test
directly, it is confusing, and may confuse people down the road trying
to build tests based on this one.
Change-Id: Idd1da91fe8d8b1e20bef469ef67728610a9ac3c1
Closes-Bug: #1527881
We stopped talking about /v1.1 nearly 3 years ago, it's in no
documentation. It should not be in our default deployed paste.ini as
it will only confuse folks.
Change-Id: Id695f60e30b14f939973e3610c7750b83a14d0d0
Currently some of the unittests are using non valid UUID format
for the FieldType UUID.
This is preparation work to add UUID validation in the
oslo_versionedobjects/fields.py.
Without this change adding validation will cause tests to fail.
Change-Id: I0ba662c26b5aa8fe03189858f793d304be612c5b
The tests use mox which isn't stable with py34 testing, there are
race failures with the assertions. This test fails in unexpected
ways in unrelated changes so we need to blacklist it from py34
testing.
Change-Id: Ieb972f4705254af4b014d79a39bd6d78ad0b6376
Closes-Bug: #1526369
Now, we can hydrate the RequestSpec object directly in the conductor and modify
the Scheduler client to primitive it before calling the RPC API.
Later changes will focus on modifying the scheduler.utils methods to play with
RequestSpec object (and possibly kick build_request_spec) but this can be done
on separate changes for cleaning that up.
NOTE: There is an ugly hack hidden in that change because of a bug
in oslo.messaging which doesn't accept datetime type for values. That will be
removed right in the next patch of the branch. Yeah, I know it's bad but it's
very temporary.
Change-Id: I916707d4dee66608e0bf7cd2d0784dafbfecda38
Partially-Implements: blueprint request-spec-object-mitaka
Matthew Treinish