os-hosts is deprecated in the compute REST API with
microversion 2.43 via change:
Ieb85653b85a1eff38a9fb0c9ff05e4cd39150ecc
So nova shell and API bindings should be deprecated as well.
Implements blueprint deprecate-os-hosts
Change-Id: I79091edf5a2569e49e79deba312456fdcdee09e1
The 2.32 microversion added the support for creating a
server with a tagged block device mapping and/or tagged
nic.
Due to a bug, block device tags would only work in the
2.32 microversion but nic tags would still work up until
the 2.37 microversion, which regressed that functionality
as well.
Both block device and nic tags were fixed again in the 2.42
microversion.
This change updates the help text for the 'nova boot' CLI
and client-side validation in the shell for the various
microversion ranges of support for both block device and
nic tags.
Co-Authored-By: Andrey Kurilin <akurilin@mirantis.com>
Change-Id: I7492b20b5d2daa0f8391abed07ef861043c3e51e
Implements: blueprint fix-tag-attribute-disappearing
Closes-Bug: #1658571
keystoneauth supports setting additional info into the user-agent string
about what the client is. Set it so that novaclient shows up in server
logs as the client.
Change-Id: I084a16f5372ec7df598505e9f925a70d26d66f69
A cinder volume remains after
the 'test_boot_server_with_legacy_bdm_volume_id_only'
functional test.
It is resource leakage. So fix it.
Change-Id: I3cacbac6468b5fad1c9666892fc57906af24b169
Partial-Bug: #1613105
The nova-cert service was deprecated in Newton:
789edad0e811d866551bec18dc7729541105f59d
We're going to remove the nova-cert service and
os-certificates API from the server in Pike, so
we need to also get started on the deprecation
in the client.
Part of blueprint remove-nova-cert
Change-Id: If3e1e40947a8ad3f665f6a96d46de8cef6a2a190
The servers which `nova list` showing are not only active servers.
This patch revises this description.
Change-Id: Ie962f79dd15c1bb0ef34f5c280f5b19b0e5705c2
These were deprecated in Newton:
aaebeb05a03e34281a091dc6dfc4672b01cdfbbb
The 'find network' convenience helper when
booting a server only works with neutron now,
and assumes the 'network' endpoint is in the
service catalog.
The functional tests are changed to use
python-neutronclient for listing and finding
the network to use. At this point, we don't
have any nova-network CI jobs that will work
with novaclient, so the non-voting mitaka
nova-network job is also being removed in change
I63b36fb8acc5c9a273e6adcb271df16d0f71031e.
As noted in the release note, the only remaining
pure nova-network CLI/API that will work is for
listing virtual interfaces, which is only implemented
for nova-network within Nova. The functional tests
for this API are removed since we don't have any
nova-network CI jobs that will test it besides
unit tests. Long-term we'll likely deprecate the
os-virtual-interfaces API as well and replace it with
the os-interface API.
Change-Id: I8c520100a0016eed3959619c71dae037ebd72939
Code changes done so that nova list command with filters run without
error when no instances are present. It shows a blank table instead of
error message.
Closes-Bug: #1624978
Change-Id: Iff879a520c607b8205a3ce5db8fc92287253dbe0
Co-Authored-By: Diana Clarke <diana.joan.clarke@gmail.com>
Create API call expectes two parameters - name and policies[*]. It is not a
complex structure, so there is no reason to support kwargs. It is better to
specify explicitly all expected parameters.
PS: removing support of kwargs is "backward compatible", since we have
validation at API side and usage of additional parameters was an error
previously.
[*] - https://developer.openstack.org/api-ref/compute/?expanded=create-server-group-detail
Change-Id: I8b40b0db450287bbc5ee8d69834aa764353dbd98
v2 and v2.1 is supported now and it ask user to use v2.x API
should be what we wanted , this already deprecated for a
couple of release, so we can remove it now
Change-Id: I8de6fdbf21ccc4969297044a49590ffcd9cd27d8
This prevents tests from hanging indefinitely, which we
are seeing in the trigger crash dump tests, which are
also skipped in this patch.
Partial-Bug: #1675526
Change-Id: If4858040187834ccdebb3f83bfbfa14d5d3251fc
The name and availability_zone positional arguments
were deprecated in Newton as part of change:
8030879330da432d4791f64fad4df24c7fc16f71
This change removes them.
Change-Id: I61031eb9eea37891f0be5d67942aaae0859065f0
These were deprecated in Newton:
aaebeb05a03e34281a091dc6dfc4672b01cdfbbb
The floating IP fixtures and GET API methods in the
manager are still used for testing the addFloatingIP
and removeFloatingIP server operations, so the manager
is moved to the test_servers module.
Change-Id: I2138e43160772c7c896bc5e93195a8169ebfe6c3
These were deprecated in Newton:
aaebeb05a03e34281a091dc6dfc4672b01cdfbbb
The SecurityGroup resource object is left
since the list-secgroup command and
list_security_group servers API code
still uses that object. The
/servers/{server_id}/os-security-groups API
is a proxy to Neutron but was not deprecated
in microversion 2.36 so it's not yet deprecated
here in the client.
Change-Id: I6fa14f43d48f1e035ef54bd2d0078506f0c6d6e0
These were deprecated in Newton:
aaebeb05a03e34281a091dc6dfc4672b01cdfbbb
Apparently we did not have any tests for this code.
Change-Id: I33c18433e57941b26a4abd290b3cd03994d26327
These were deprecated in Newton:
aaebeb05a03e34281a091dc6dfc4672b01cdfbbb
Since this is the last of the deprecated contrib extensions,
we can also deprecate the 'only_contrib' parameter from the
novaclient.client.discover_extensions method.
Change-Id: Ie2e3fdc4e044f6eb304724d16a7d0f1f7ba705fd
These were all deprecated in Newton with change:
87c1b5311b2e641564305a4753b989b6498775b1
So now we can remove them.
Change-Id: Ic74a989b8a6565cc52ab82440fab8605a4b78e6b
The name and availability_zone arguments to aggregate update were
replaced by optional parameters in change
I778ab7ec54a376c60f19dcc89fe62fcab6e59e42. However, the '--name' and
'name' arguments in the parser would conflict, resulting in only the
deprecated argument working. Thus, attempting to update the name
on an aggregate using --name would end up doing a PUT with no new
name provided.
Note that there were unit tests for this, but they were not catching
this problem. So, this removes those tests and adds functional tests
to poke it.
Change-Id: Ifef6fdc1a737dd219712a4525d4e34afd3fbd80c
Closes-Bug: #1673789
If you pass incorrect formatted metadata to the 'boot', 'rebuild'
and 'image-create' apis returns following error:
ERROR (ValueError): dictionary update sequence element #0 has
length 1; 2 is required
Caught the ValuError and raised argparse.ArgumentTypeError with
proper error message.
Closes-Bug: #1668549
Change-Id: I14a30b93f4a916fc04610f9e475c12eb352e38c5
Currently, Tags(list) and Metadata(dict) fields of instance will
firstly transformed to str using jsondump first when display. And
cannot be correctly transfomed and displayed afterwards.
This patch adds ensure_ascii=False to the transform function thus
those fields can be correctly tranformed and displayed afterwards.
Change-Id: Ib4e7a34f3b19db89280cc73053acbac8c8816f85
Closes-Bug: #1669683
Change adf7d1e48c619579c2fc430229173264db45033e removed the
deprecated network proxy CLIs but missed a couple of functional
tests. These were caught because the mitaka functional job runs
nova-network which actually runs these tests, but is non-voting.
The functional jobs that run on master are using neutron and skip
these tests.
Change-Id: I5f66905a315cb36f094e30e673629893cf4bdc49
Closes-Bug: #1669043
This patch adds deprecation warning for usage of
cell_name argument in migration_list command.
Change-Id: I54468682d5391668a513e708e26bc3c165c95ca1
Related-bug: #1668743
