The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Ib1a25cc31b6802655f576711dab38ddfcb73bbdb
Replace the data of FAKE_CREATE_ENCRYPTION_TYPE and
FAKE_INFO_ENCRYPTION_TYPE as the API document described
Change-Id: I892e27c4219da956c452fda067ee5fef08295c30
Closes-Bug: #1836133
This relesenote also mark end of support for Pike release
in Tempest as Pike is in EM state[1].
[1] https://releases.openstack.org/
Change-Id: I92c7a7d125ca62466704bc9416b2dfe9f1d8729d
In ServersTestMultiNic, all testcases will be skipped if
CONF.service.neutron is not available, so skip_checks should
be used.
Change-Id: Id10be3ddb346e8f8b07568fce664e202d58a46c9
This commit adds ranger-tempest-plugin to the blacklist. The plugin
looks like very new and it looks it doesn't work correctly yet. So, it
might be better to skip to sanity for the plugin now.
Change-Id: I6d5d647d92916e5b62e8c67094d04f028e25ee67
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note: This diverges from the Train goal as it does not drop the
openstack-python35-jobs. As tempest is branchless it needs to continue
supporting Python 3.5.
Change-Id: Ie702ca637afb8229b6e605abcec25550bc9a0673
Story: #2005924
Task: #34240
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-object-storage'
gate template for swift gate which will run only Swift, Cinder and glance tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-object-storage template on swift gate.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: I70851d41174462b83cc8c525cecdb1b3d65e4ec7
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-compute'
gate template for nova gate which will run only nova, neutron, cinder
and glance tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-compute template on nova gate.
It will also help to disable the non-nova related serviecs and tests which
cannot be disabled from tempest-full job.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: I807d4cac6214395df292a6955686ea44677c3481
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-placement'
gate template for placement gate which will run only nova and neutron tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-placement template on placement gate.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: I200197e2fb57879aaeb382266d6309f0d1137b0c
test_server_connectivity_cold_migration_revert has begun failing again
pretty consistently (though not 100%) as soon as we merged the match
to un-skip it. Start skipping it again until we work out the issues.
Change-Id: I9b4cf79d223cbb399b5857571114665cd03e8921
Related-Bug: #1836595
tempest cleanup returns an error when it's initializing a saved
state, because it uses already deprecated v2 client.
The patch makes tempest cleanup use keystone role v3 client.
Closes-Bug: #1788561
Change-Id: Id607dec012ce48af6d4c7ee263a90c3ea2e1799c
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-storage'
gate template for cinder gate which will run Cinder, Glance, Swift and
Nova tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-storage template on cinder and glance gate.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: Iae7d26325228aad0edb94f7e191c8fd0d60e1362
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-networking'
gate template for neutron gate which will run only nova and neutron tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-networking template on neutron gate.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: Ifca8172f2f929105af4bad8ab72b05c2c45a5f58
This commit fixes the tempest run documentation indentations for more
appropriate rendering[0]. Currently, it's rendered as a quote which is
weird.
[0] https://docs.openstack.org/tempest/latest/run.html#test-selection
Change-Id: I764cfff7dd07214fa44dacfa2a86476471e8fb20
In test
tempest.api.compute.servers.test_attach_interfaces.AttachInterfacesUnderV243Test.
test_add_remove_fixed_ip
functions _wait_for_ip_increase() and _wait_for_ip_decreace() will
now filter out floating IPs from the list of server IP addresses
to compare only number of fixed IPs as this test is only about adding
and removing fixed IPs to the server.
Change-Id: I38c17da4ff492569cf572718c4443ebcc4718f62
Closes-Bug: #1834758
This commit removes the nova-lxd plugin from the blacklist. The proposed
patch was already merged, so this plugin should pass the sanity job now.
Change-Id: I72eb62af993bc978127185a1aed0763af18ce9f3
This commit removes x/networking-ansible from the tempest plugins list.
The original patch[0] was abandoned because networking-ansible took a
different approach[1] for the testing. So, it's not a tempest plugin
anymore.
[0] https://review.opendev.org/#/c/634647/
[1] https://review.opendev.org/#/c/634918/
Change-Id: I554c438f27a7032f31e56eac2aac110e08bb3d7d
This commit removes the cyborg-tempest-plugin entry from the BLACKLIST
since the patch was already merged and this plugin should pass the
sanity job now.
Change-Id: Ifec2e45761961bc4dfc3b5c11709c0ac9e81855f
This is to fix invalid assertIsNone state of
"self.assertIsNone(None, self.run_cmd._build_regex(args))".
Change-Id: I4878632cabc75097b6e975a5a2dcce6945d30958
Ib346d383c430d5151d9aafa6e856dd0a7cae8a23 incorrectly attempted to pass
this as imageRef leading to duplicate arguments being used when calling
the servers client to create the server.
Closes-Bug: #1834461
Change-Id: Ic913176b429b3465dcdbc2e4f44eea32f0b17dfa
Flavor id is not returned in the server response after microversion 2.46,
but we can use base.assert_flavor_equal to check flavor before and after
microversion 2.46.
Change-Id: If04005a3ff5ef4b1faa4d2179ba2987abdd5ef04
This reverts commit 2a4641c056f3ca0157d1c4ea6cd8e45f85e9213e.
Due to change I9e0cffb889c94713c7f28812918103a5d97cefeb in nova
the bug is likely fixed in the gate so we can unskip it for our
standard gate testing.
Note that this change will depend on a nova patch to fix how
network-vif-plugged event handling works for OVS hybrid type
ports to (1) make sure that change works in a multi-node scenario
and (2) to not unskip this test until that bug is fixed.
Depends-On: https://review.opendev.org/667177/
Change-Id: I3911994392ec2050f5d5b4bbf83de4f329b6e372
Related-Bug: #1788403
