Ic2e5bd127c9f3a0f2807a25f29d8693baf3d65f2 of oslo.log has changed
the description of use_syslog, but current tempest.conf.sample does
not contain this change. As the result, the pep8 test continuously
fails on the gate now.
This patch fixes this description.
In addition, this patch adds fake body message to NotFound in
javelin test for avoiding the gate problem.
These gate problems happened at the same time, so this patch contains
mutiple purposes but that is necessary for fixing at the same time.
Closes-Bug: #1468141
Closes-Bug: #1468149
Change-Id: Iada215718651dc153b977008b376a956247ebc5d
Our remote ssh code makes all kinds of assumptions about the shell and
path of the guest. Recently some code was added to the command to generate
errors more promptly but it does not work if the shell is /bin/sh. This
commit allows the user to configure tempest with a desired prologue to handle
this case. It does nothing to solve the more general problem and, like the
other image-related options, cannot be customized individually for various
images that tempest may use.
Debug logging of remote commands was also added.
Change-Id: I669dd4386ffb539dad88a9487bef6c172b5d65fa
Closes-Bug: #1465682
This commit adds a new config option to the auth section,
create_isolated_networks, to disable tenant isolation from attempting
to create an isolated network stack on each created tenant. This is
needed because in certain neutron configurations the extra resource
creations are not need or not allowed.
Change-Id: I0899a43709a0cb2967376e914248d2ad4a37773a
Closes-Bug: #1447829
This commit updates the tempest sample config file to
include changes in the latest oslo.log release, 1.2.0.
This is needed to unblock the sample config generation
job which is failing because the in-tree tempest sample
config file differs from what is generated with a fresh
venv.
Change-Id: Id40310712ecda13d65cfd68bdaf4ea91dc7687fe
Default domain is part of Keystone APIv3 domains feature added in Grizzly
backward compatibility for APIv2 which is not aware of domain concept.
Summary of scope this change:
* added new variable 'default_domain_id'
in tempest.conf (default value 'default')
* new test: default domain must exists (backward compatibility)
Change-Id: Ib77d259e2f377ff19e2cf40fa164f42c0669ea56
Some images require additional properties.
This change adds dictionary option "img_properties"
to the "scenario" config section.
For example, to work with Parallels Containers, specify vm_mode:
img_properties = vm_mode:exe
By occasion, we fix handling properties in _image_create in scenario/manager.py:
disk_format is an x-image-meta-* option, and kernel_id, ramdisk_id are properties.
Change-Id: I2d3714eb899faad67a867a630c1d72d1fd8ee74f
This commit adds to cinder client a bootable capability
supported flags are True or False.
And a testcase for changing the bootable flag from true to false.
Update bootable volume is not supported on icehouse
Added new flag under config.py - to enbale this feature by request
Change-Id: Ia23cab169c46d631444399ab1edd93c43cfb7ef5
This commit adds a new config option to the config group to trigger
all the validation code. It also deprecates the run_ssh option in the
compute group since this will eventually be used globally. The intent
of this option is so that it will trigger both the creation of any
validation resources as well as used as run_ssh was originally
intended, to trigger ssh into nodes when needed.
Closes-Bug: #1453936
Partially-Implements: bp ssh-auth-strategy
Change-Id: I7d04f81457fc564ed82872e602746c8162fef24c
The cli tests have been marked for removal for ~6 months and the
framework was the first thing included in tempest lib. There has
been more than enough time for all the projects to pick this up
in the client repos. So let's remove it all!
As part of this a couple of missing entries for tempest's
requirements.txt were found. These dependencies were being installed
by the clients so the fact they were missing was never noticed prior
to this. This commit also adds these missing entries back into the
requirements file.
Change-Id: I4f8638f1c048bbdb598dd181f4af272ef9923806
Nova change Ib38eaf412cb51a9cbfc443c5ec15c5797265ddae adds support for
doing live migration of a paused instance, this adds the test to cover
that scenario.
This also depends on a series of devstack-gate changes to support
multi-host testing in the experimental queue. Specifically, this is
tested in the check-tempest-dsvm-aiopcpu-full job.
Depends-On: I89b7e390bf1cf4f2eccabca2e31a9d1b6b270677
Co-Authored By: "Matthew Gilliard <matthew.gilliard@hp.com>"
Related-Bug: #1305062
Change-Id: I5c6fd3de7ea45d1851bb40037c64ad7fb5e6dc48
Use formatter from oslo_log instead of tempest.openstack.common.log
which got removed as of 583ce2c043a64778ae20a957f10cd5029e2e3230
Change-Id: I0d9334c51d50f649fdb7e34fd7c2f3d807b80601
This commit cleans up some details in the accounts.yaml sample file
and the tempest configuration guide to provide missing details about
how to create and use an accounts file. Specifically it adds more
detailed comments to the sample file about each section, and in the
config guide it removes obsolete sections and adds some missing
details.
Change-Id: Ic11335fe1215ab0625ea2308ccc75d22a284c432
Closes-Bug: #1447851
BP MTU selection and adervertisement requires sending pkts of known
sizes to verify MTU. This patch allows basic MTU testing via the
linux_client
Change-Id: Ia98ad49bad9ebbf783de599689b4684d31fadca6
This commits adds support for specifying the network to use with a
user/tenant into the accounts.yaml file. You can only specify a single
network which will be the network used for all that requires a
pre-existing network. This also means regardless of which cred provider
is configured the fixed_network can assume a TestResource object will
be returned from a get_creds call. As part of this change a common
method to return the full network dict from a just a network name is
abstracted out into tempest.common.fixed_network module since this
same method is needed to have the accounts file provide a network by
name.
Partially-implements: bp test-accounts-continued
Change-Id: I6f5ac1239d18f2935847b385a08de608f40fdda5
This patch add new configuration options for the multiple strategies
for ssh access to VMs.
Partially implements: blueprint ssh-auth-strategy
Change-Id: I16cdbe0982aa35b752828054b6be2cae6c51c6ef
Adding the ability to skip test_update_instance_port_admin_state
when this operation is not supported by the test environment.
Closes-Bug: 1436839
Change-Id: Icda251c46e2fefcc80b0c712d6f42d76a7d247b7
network and router are both top-level network
resources and router should be represented in
the yaml file both for clarity and also having
router name exposed in yaml file is useful for
building white list for tempest cleanup.
In addition horizon also lists networks and routers
as top-level network objects. Adding router to the
test account output aligns with this existing pattern.
Change-Id: Iddebba793a978281f698ea10c167dc0a8765d785
Introducing a sample file in etc/ similar to the existing ones for
tempest.conf or accounts.yaml. This file can be used as a concrete
example of how to use Javelin.
Currently some resources are missing from the file (like volumes,
routers, and more importantly servers) and could be added in a later
commit.
Change-Id: I3e0d06c7654ad30c42e435a19106c6633144c9b5
https://wiki.openstack.org/wiki/Glance-deactivate-image
Adding the api support for these commands.
Deactivate and reactivate image action is done by admin tenant.
- Added admin folder to image tests
- Added support for admin image classes for v1 and v2
- Added config deactivate_image , this feature is not running on
icehouse
- Added a testcase for image deactivate.
Depends-On: Ia1d3d811bd57d3de16d397cfab341e8d0f17cb69
Change-Id: I7880f0e2646ce8660e035ebaa19a60f5bf271b64
In Kilo, Ironic introduced Node cleaning - an optional (but default
enabled) step which is performed after deletion and before returning a
node to the available pool.
Devstack change https://review.openstack.org/#/c/168175/ overrides the
default to 300 already. This patch is just copying that default into
Tempest's config.
Co-authored-by: SHIGEMATSU Mitsuhiro <shigematsu.mitsuhiro@lab.ntt.co.jp>
Change-Id: Icd5fe47bbaba189ef446f976f01309a7e3560a69
This commit removes support for using an accounts.yaml file with the
non-locking provider. There is no reason the non-locking provider
would ever need to be used with an accounts.yaml file because the
locking provider supports running serially just fine. (which would be
the sole use case for accounts file with the non-locking provider)
Doing this relegates the non-locking provider to just handle the
legacy config options for providing credentials.
Removing this code path provides the advantage of removing a double
maintenance burden for the non-locking provider, in addition to
simplifying the config and user story around the cred providers. It
also turns out this config permutation was never properly tested and
didn't actually work.
Change-Id: I8088d75897589203264ae29326fe9901c3457cc3
When we added support for using the fixed_network_name config option to
specify the network to boot with in a multi-network env a couple of
configuration edge cases were not taken into account. First the case
of misconfiguration was not handled at all this would cause an ugly
IndexError exception to be raised because no matches were found for
the name specified in config. The other was since the default config
option was set to 'private' and fixed network name is always used when
configured the default for single network environments broke if the
single network. This commit addresses these by removing the default
value for fixed_network_name (and making the help more clear) and
having fixed_network_name handle the misconfiguration case more
clearly by raising an InvalidConfiguration exception.
Change-Id: I06ac0605a1a7e35d1af9a93a3bfc387a78f8be1c
Closes-Bug: #1437328
This option, originally added in
I81cc39fed392fce9dfbda5683ffba29eeba936be was disabled by default for
Xen, and isn't supported by libvirt due to bug 1398999. Provide a better
help message explaining why this should be off for libvirt.
Change-Id: Id8f9ead99b5d5713172c9b012b771098fdee7b1c
Depends-On: I89b7e390bf1cf4f2eccabca2e31a9d1b6b270677
Cirros images allow connection with root and cirros by default.
Interactive sessions for root are not allowed. This will change the
default user to cirros since it allows interactive ssh sessions.
See also https://bugs.launchpad.net/cirros/+bug/1437350
Change-Id: If929ce7a3df944bd17c7f4e3042a6aea0c318b2c
Support using v3 to in credential providers:
- load v3 credentials from YAML if auth_version == v3
- create v3 credentials in isolated credentials is auth_version == v3
Credentials are provisioned in a configured domain (by name), or in the
admin domain if no specific domain is configured.
Support requesting a specific version of credentials from
credentials providers.
Depends-on: Iaae9286ecc6f019d36261a5c450068a650e24a28
Change-Id: Id1ffa35c35f7badd0a35140229554ddf138a3fef
This commit changes all the uses of the old AdminManager and Manager()
constructs to use cls.isolated_creds to provide user credentials from
whatever the configured credential provider is being used instead of
assuming it's the non-locking accounts provider without an accounts.yaml
file. As part of this we need to add a heat option for the stack owner
role so that we can request the creds by that role. The heat tests were
previously making an implicit assumption about the configured user having
that role assigned. Which while true in devstack today, it isn't
necessarily the case everywhere.
Depends-On: Id98a83f0a716de0fdb5f36d03407364830e8fa5f
Closes-Bug: #1433723
Change-Id: Ie071cb2cb6add591a60c9d76a12c95b7fb5ee539
This reverts commit 8ec99feafebd5ee67a0f4c34bcd5a30d8d42ed97
The neutron job on stable/icehouse was running more tests than what the
neutron-icehouse compat job was running against tempest changes on
master, that's why we didn't catch this when the change on master to add
the test was under review.
Note that stable/juno neutron jobs were not running these tests either
because the router extension isn't enabled.
The difference was we didn't have change
I7c80e3bfe4962c3e8c94736af21ff215cd98f7f3 on stable/icehouse or
stable/juno in devstack before the new test merged, which broke
stable/icehouse.
Now that devstack is fixed on stable and will run these scenario tests
we add a 'preserve_ports' config flag to compute-feature-enabled so it
can be toggled from devstack.
For stable branches we won't run the test since the code doesn't work in
Nova on stable (and won't be backported). For master devstack, we'll set
preserve_ports=True so the test does get run. We can remove the option
after juno-eol happens.
Devstack change: I214baa3b861e29bedf6bb7b50534ac2286676dd1
Related-Bug: #1431724
Change-Id: I95469e4c2f4aa2bc4e6342860a9c222fb4fa7e16
Use graduated libraries where available and update the incubated modules
that remain.
Update imports for libraries that were being used already to avoid the
'oslo' namespace package.
Update config file for creating example configuration files and provide
a new sample file based on the options defined in the libraries.
Note: because of the number of libraries involved there is no real way
to break this change up into smaller pieces. Fortunately, most of the
changes are just to import statements.
Change-Id: Ia0de957b681cb924a57af98d99a9389ee234ed5b
There are no remaining heat tests which require heat-cfntools on
the test image, so orchestration tests can just use [compute] image_ref
(AKA cirros).
test_neutron_resources has been modified to use curl instead of
cfn-signal.
This will close tempest bugs where fedora boot times out in general
gate jobs.
Change-Id: Ic70c4b5859183b9ebc716dec3095cefc62be5af7
Closes-Bug: #1430524
The latest release of oslo.config generates a line
for reach of the choices for a StrOpt. We should update
the tempest sample config with the latest output.
Change-Id: Ibed8646c774c33478d8ffc9917e835e565720a18
This commit adds support for requesting credentials by a role from the
credentials providers. This entails 2 things, first adding support for
specifying roles in a test-accounts file with test-accounts based
providers and secondly adding support to isolated-creds to assign
arbitrary roles on credentials requested by role.
Change-Id: I6a0f0539d41e0cf3d04414964b289447194d2793
Partially-implements: bp test-accounts-continued
Many people running into the issue of forgetting
to allow tenant isolation when running tempest in parallel.
Since the parallel is the `default mode`, the default config
should support this use case.
Change-Id: Ia30cfbc239c8b8628ac0926424c4100d013cd620
It's possible to launch an instance with virtual interfaces
either by specifying the network the interface should be attached
to or the port.
There are cases (e.g. SR-IOV) where it's only possible to launch
an instance with a pre-created port.
Enabling the creation of a port with known vnic_types (Currently
'normal','direct' and 'macvtap') and launching an instance with this port
attached.
Nova support Neutron SR-IOV ports https://wiki.openstack.org/wiki/Nova-neutron-sriov
Change-Id: Id5cbd50d285ac0c7e8099c30151ace9d99f02020