reno doesn't currently handle missing branches so we need
to use the liberty-eol tag to fix the release note job in
the gate now that origin/stable/liberty is gone.
reno will eventually check for the -eol tag when a stable
branch isn't found in:
I41ab682f081e7fd39ea534b7e2180c2109ca34ef
Change-Id: Ie54f69f5c1f91a3781c876f035fe9ed838e11c08
At first, the 'attachment_id_resp' in parameters.yaml was defined
as 'required' in I3789a4ad36e30728024f2aa122403b0e53b1e741
for os-volume_attachments.inc.
Then it was changed to 'optional' in
I0c1d183c5aaf6fb796be30fa5627bd5644ea689f
for os-volumes.inc.
So currently 'id' (attachment_id) parameters in
os-volume_attachments.inc are wrong.
They should be 'required'. So fix them.
Change-Id: I403a9eb1b08a840cbb2b82cb37f1b49c6edb87c9
Closes-Bug: #1608842
Currently we have lot of validation code inside
server tag controller class which can be moved to
json schema.
Same can be reused on other place also.
For example, microversion 2.40 adds server tag while
boot. Same schema can be used there.
Current python code validation shows conceret error message about each
tag where using json schema error msg will be like below-
For requesting tags more than max limit:
Invalid input for field/attribute tags. Value: ['0', '1', '2', '3', '4',
'5', '6', ...] is too long
For requesting tags more than char limit:
Invalid input for field/attribute 0. Value: aaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.
'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa' is too
long
I think those error message are clear enough to understand the wrong
tags.
Change-Id: I457cf630aeae9034c0b175d016148a1d50a0b469
We're seeing race failures in this test because the ip_addresses
can show up in an unexpected notification depending on when
allocate_for_instance in the neutron network API completes and
the instance.info_cache.network_info data gets stored in the
database.
We can resolve the race by using SpawnIsSynchronousFixture which
makes the allocate_for_instance network API a blocking call
until the network_info is returned, and by that time it's stored
in the instance_info_cache in the database which is where the
versioned notification pulls it from in _send_versioned_instance_update.
Change-Id: Id482220b8332549a07efb4f82212d74e6e7b9d6c
Closes-Bug: #1649403
The nova/tests/functional/api_sample_tests/test_servers.py contains the
ServersSampleBase class, and in its class definition creates a
'user_data' attribute by base64 encoding a string. However, this will
not work in Python 3, as the base64.b64encode() method requires bytes,
not a string. As a result, importing the test class fails and no tests
get run.
Note that this change doesn't fix all tests to work under Python 3; it
simply fixes the bug that prevents the tests from running at all under
Python 3.
Closes-Bug: #1632856
Change-Id: I35a7b02132bed0387a173b339f6204bf0e3269de
Change ff6b9998bb977421a5cbc94878ced8542d910c9e enforces in
a database migration that you've run the simple_cell_setup
command for cells v2 but the instructions in the error and
in the release note said to use 'nova-manage db' when it should
be 'nova-manage cell_v2'.
Change-Id: I8e71d1c7022d1000f26b7c16ed1c56f6e87ab8ac
Closes-Bug: #1649341
The 'name' filter values passed to the ResourceProviderList object
are expected to be unicode. When not unicode the tests produce
warnings which are noise since that's not what is actually being
tested. This change makes the values unicode and thus shuts up the
warnings.
Change-Id: Iebc50ff2ced120d5004fa6d053401469097beb1b
