summaryrefslogtreecommitdiff
path: root/.zuul.yaml
Commit message (Collapse)AuthorAgeFilesLines
* Bump nova-ceph-multstore timeoutDan Smith2023-05-101-1/+2
| | | | | | | | | | | | | | | The recent change(s) to enable a lot more SSHABLE checks puts the runtime of the ceph job really close to the 2h timeout even when things are working. Sometimes it times out before it finishes even though things are progressing. Bump the timeout to avoid that. Also bump us to 8G swap to match what is set on the parent ceph job when we upgraded to jammy. We could just unset this, but better to pin it high in case that job (defined elsewhere) changes. Our job is the largest ceph job, so it makes sense that it keeps its own swap level high. Change-Id: I6cefd87671614d87d92e4675fbc989fc9453c8b9
* Remove focal job for 2023.2Dan Smith2023-04-241-13/+0
| | | | | | | | | | | | | | Neutron also flipped to python>=3.9 on all their repos this morningi[1] which means we can't install neutron on focal at all. I'm not sure if that's going to get reverted at this point, but even if it is, it's going to take a while to undo. As noted in the comments and the original commit[2] that added this job, it was intended to be removed when we dropped focal from the test interface, which we have now done. 1: https://review.opendev.org/q/topic:bug%252F2017478 2: https://review.opendev.org/c/openstack/nova/+/861111 Change-Id: I5be638a702629e07ec9c88bd67bb9b7f1212f7fc
* Add grenade-skip-level-always to novaDan Smith2023-03-231-1/+3
| | | | | | | | | | This makes us test N-2->N even for non-SLURP releases. Ideally we would continue to keep this working, even though we don't have to. But, even if this highlights some breaking change and we have to drop this job, the sentinel will be useful. Depends-On: https://review.opendev.org/c/openstack/grenade/+/875990 Change-Id: I2b21e7d5f487f65ce4391f5c934046552d01a1e2
* Make nova-next reduce mysql memoryDan Smith2023-03-031-0/+1
| | | | | | | | This job is known to fail due to OOM in various places, so this makes it enable the memory footprint reduction flags for devstack that we already use in the ceph job. Change-Id: Ibf1bdb55018a329075e31058f83ab95331c84ebb
* Use mysql memory reduction flags for ceph jobDan Smith2023-02-211-0/+1
| | | | | | | | | This makes the ceph-multistore job use the MYSQL_REDUCE_MEMORY flag in devstack to try to address the frequent OOMs we see in that job. Change-Id: Ibc203bd10dcb530027c2c9f58eb840ccc088280d Closes-Bug: #1961068
* Enable new defaults and scope checks by defaultGhanshyam Mann2023-01-101-0/+34
| | | | | | | | | | | | | | | | | | | | | | As discussed in PTG, we need to test the new RBAC in the integrated gate and accordingly enable the new defaults and scope check by default. A new integrated testing job has been added and results show that the new defaults and scope checks are working fine. During testing, we found a few bugs in neutron policies but all are fixed now. enforce_scope and enforce_new_defaults are oslo policy config options but they are per service level and the default value can be overridden. Oslo policy 3.11.0 version allows to override the default value for these config options[1] so upgrading the oslo policy version in requirements.txt Depends-On: https://review.opendev.org/c/openstack/devstack/+/869781 Depends-On: https://review.opendev.org/c/openstack/placement/+/869525 [1] https://github.com/openstack/oslo.policy/blob/3.11.0/oslo_policy/opts.py#L125 Change-Id: I977b2daedf880229c8d364ca011f2ea965b86e3a
* Merge "Update gate jobs as per the 2023.1 cycle testing runtime"Zuul2022-12-201-4/+14
|\
| * Update gate jobs as per the 2023.1 cycle testing runtimeGhanshyam Mann2022-11-221-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As per 2023.1 testing runtime[1], we need to test on Ubuntu Jammy (which will be taken care by tempest and devstack patches to move base jobs to Jammy) and at least single job to run on Ubutnu Focal (for smooth upgrade). Also, python 3.10 testing is voting now. This commit adds a new job to run on focal which can be removed in future cycle when testing runtime drop the requirement of Focal testing. Also, make python 3.10 functional and unit test job as voting (openstack-tox-py310 is running as part of generic template so we do not need to explicitly add that) [1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html Change-Id: Ia43f73dba00b0b5932939bcc7d11b97a83072ee3
* | Temporary skip some volume detach test in nova-lvm jobGhanshyam Mann2022-11-281-2/+3
|/ | | | | | | | | | | | | | A few tests related to volume detach are timeout in nova-lvm job (failing 100%[1]). Root cause of timeout is not known and it may take time to find and fix the issue. To unblock gate and keep runing rest of the tests in lvm job, let's skip the failing tests until they are fixed. Related-Bug: #1998148 [1] https://zuul.opendev.org/t/openstack/builds?job_name=nova-lvm&branch=master&skip=0 Change-Id: Id29ce352df84168d0a45512e2c59820aefc75943
* Test ceph-multistore with a real imageDan Smith2022-11-091-1/+7
| | | | | | | | | | | | This inflates the cirros image to 1G for a more realistic scenario. Technically we should have been doing something like this all along, as the deployment guidance for ceph is to use a raw image, not a qcow2 one, so this also increases our accuracy to real-life. We also need to up the volume size tempest uses for various tests to make sure we will fit. Change-Id: I5c447e630aaf1413a5eac89c2e8103506d245221
* Enable glance location tests on ceph-multistoreDan Smith2022-11-021-1/+7
| | | | | Change-Id: I5672d2e1352bd5236a92630234e1261a782bc539 Depends-On: https://review.opendev.org/c/openstack/tempest/+/861390
* Merge "Remove the periodic Centos 8 job"Zuul2022-10-051-4/+0
|\
| * Remove the periodic Centos 8 jobafariasa2022-10-031-4/+0
| | | | | | | | | | | | | | Centos 9 fips tests are already merged on Nova and Centos 8 jobs were already replaced by Centos 9, this patch will delete a Centos 8 periodic pipeline that should have been deleted on previous patcc. Change-Id: Ib735e9b52915639006bb08424d83f8ee39113d4f
* | Switch to 2023.1 Python3 unit tests and generic template nameOpenStack Release Bot2022-09-161-2/+2
|/ | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for antelope. Also, updating the template name to generic one. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Ieecbed5216c1ed47743bc2b74745c0a91bb105a3
* Merge "Test setting the nova job to centos-9-stream"Zuul2022-09-141-3/+2
|\
| * Test setting the nova job to centos-9-streamAde Lee2022-07-131-3/+2
| | | | | | | | | | | | Depends-On: https://review.opendev.org/c/openstack/tempest/+/831607 Change-Id: Ic8da6ee0313a911d742190ea5b0d4362cb6aef2f
* | nova-live-migration tests not needed for IronicJay Faulkner2022-08-171-2/+17
| | | | | | | | | | | | | | | | Ironic does not support live migration, so we will skip these tests if the only changed files are in Ironic virt driver to ensur we don't waste resources or time trying to run unneeded tests. Change-Id: Ieb5ac3bb93af6a950acff4d76d0276096a6a24dd
* | Remove double mocking... againBalazs Gibizer2022-08-081-1/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | I thought we fixed all the double mocking issues with I3998d0d49583806ac1c3ae64f1b1fe343cefd20d but I was wrong. While we used both mock and unittest.mock the fixtures.MockPatch used the mock lib instead of the unittest.mock lib. The path Ibf4f36136f2c65adad64f75d665c00cf2de4b400 (Remove the PowerVM driver) removed the last user of mock lib from nova. So it is also removed the mock from test-requirements. This triggered that fixtures.MockPatch athat started using unittest.mock too. Before Ibf4f36136f2c65adad64f75d665c00cf2de4b400 a function can be mocked twice once with unittest.mock and once with fixtures.MockPatch (still using mock). However after that patch both path of such double mocking goes through unittest.mock and the second one fails. So this patch fixes double mocking so far hidden behind fixtures.MockPatch. Also this patch makes the py310 and functional-py310 jobs voting at least in the check queue to prevent future changes adding double mocks. Change-Id: Ic1352ec31996577a5d0ad18a057339df3e49de25
* zuul: Put Centos9 Stream job periodic-weekly and experimentalSylvain Bauza2022-07-121-10/+4
| | | | | | | | | | | | | | | | This patch is a followup on 45c0a3884b6b4c0b9a6b1b3cef47651f5504502e As agreed on the Nova weekly meeting [1], we won't put back C9S job to voting and we'll rather put it on both experimental and periodic-weekly pipelines. In order to insure we will monitor the status of those runs, we'll check the status of the job during every Nova meeting happening weekly. In order to trigger potential race conditions, it was acted to provide an experimental job for C9S too. [1] https://meetings.opendev.org/meetings/nova/2022/nova.2022-07-05-16.00.log.html#l-52 Change-Id: I2de4d90202fd7e735026150f79409d51f2d70e0e
* update nova-next and nova-ovs-hybrid-plug to disable linuxbridgeSean Mooney2022-07-071-4/+4
| | | | | | | | | | | | | neutron now declares linuxbridge experimental and requires it to be enabled by a new config option. We do not set that in these jobs so the neutron server fails to load since we enable the linux bridge mech driver. we do not actully use linuxbridge in these jobs so this patch just disables the mech driver. Change-Id: I129a850c3327498d26d899c7709f5749622afdd8 Closes-Bug: #1980948
* zuul: Temporarly put Centos9 Stream job non-votingSylvain Bauza2022-06-171-0/+6
| | | | | | | | | | | | | Due to the bug below, all the nova patches are failing. I accordingly propose to make the job non-voting as it would allow our gate to ressurect. Of course, this is a transient solution and we need a proper fix for the job in order to have Centos 9 Stream support back in place ASAP. When the job is back OK, please make it voting again by reverting this patch. Change-Id: I5c3fff65fd6d9e4f3632d1ec62ae3f1f9cfbe626 Related-Bug: #1979047
* Revert "zuul: Skip block migration with attached volumes tests due to bug ↵Lee Yarwood2022-05-181-4/+2
| | | | | | | | | | | | | | #1931702" This reverts commit 7c478ac0992d9713c0fd7ea0a0498f0b7f92ce0d. With the resolution of bug #1945983 in devstack we should also be able to start testing block migration with attached volumes once again. Closes-Bug: #1931702 Depends-On: https://review.opendev.org/c/openstack/devstack/+/812391 Depends-On: https://review.opendev.org/c/openstack/devstack/+/812925 Change-Id: I1cb7a8f76c372d19227315361ecf5ff730ec6c36
* Merge "Drop lower-constraints.txt and its testing"Zuul2022-05-171-1/+0
|\
| * Drop lower-constraints.txt and its testingGhanshyam Mann2022-04-291-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | As discussed in TC PTG[1] and TC resolution[2], we are dropping the lower-constraints.txt file and its testing. We will keep lower bounds in the requirements.txt file but with a note that these are not tested lower bounds and we try our best to keep them updated. [1] https://etherpad.opendev.org/p/tc-zed-ptg#L326 [2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal Change-Id: Ifbc383f6d4c858189cee55e67b4d4274d9c3358a
* | Merge "Add Python 3.10 functional jobs"Zuul2022-05-131-0/+24
|\ \
| * | Add Python 3.10 functional jobsStephen Finucane2022-05-061-0/+24
| |/ | | | | | | | | | | | | | | These are currently non-voting since we don't care about this stuff for Zed. It does get us ready for a 3.10-having future, however. Change-Id: I7740dafd6523eca27fa4e725d7eaf8558e434779 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* | Enable live_migration_events in nova-ovs-hybrid-plugBalazs Gibizer2022-05-041-0/+6
|/ | | | | | | | | | | | | | The flag was added to prevent the source host neutron agents to trigger a vif-plugged event too early during a live migration. But actually it can be used in a more generic sense as the code filter on migration_to binding profile attribute. We saw too early vif-plugged events from neutron during evacuation in post part of the nova-ovs-hybrid-plug job. So this patch enables the workaround flag for this job too. Closes-Bug: #1971563 Change-Id: Ifd20ece3a4f126da16f077247c2f1e072edb7163
* Merge "Add nova-emulation to the experimental queue too"Zuul2022-04-291-0/+1
|\
| * Add nova-emulation to the experimental queue tooBalazs Gibizer2022-04-061-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | This job was moved to periodic in the past to save CI resources. However sometimes it can be valuable to trigger it on a given review. To be able to do that easily this patch also adds the job to the experimental queue. Then the following gerrit comment can be used to trigger it: check experimental Change-Id: I6a018b57de5afe772c2478aff836b39227dce228
* | Move centos stream testing to centos-9-streamGhanshyam Mann2022-04-251-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Zed cycle testing runtime, we are targetting the centos 9 stream - https://governance.openstack.org/tc/reference/runtimes/zed.html With dropping the python 3.6 support, project started adding python 3.8 as minimum, example nova: - https://github.com/openstack/nova/blob/56b5aed08c6a3ed81b78dc216f0165ebfe3c3350/setup.cfg#L13 with that, centos 8 stream job is failing 100% - https://zuul.openstack.org/build/970d029dc96742c3aa0f6932a35e97cf - https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-8-stream&skip=0 QA is dropping the centos-8-stream testing and support - https://review.opendev.org/q/topic:drop-c8s-testing This commit replace tempest-integrated-compute-centos-8-stream job to tempest-integrated-compute-centos-9-stream. Depends-On: https://review.opendev.org/c/openstack/tempest/+/839274 Change-Id: I516b9d732ccea6e12904a1612530bce273d06587
* | Update python testing as per zed cycle teting runtimeGhanshyam Mann2022-04-211-29/+4
|/ | | | | | | | | | In Zed cycle, we have dropped the python 3.6/3.7[1] testing and its support. Removing the py36 centos8 job as well as updating the python classifier also to reflect the same. [1] https://governance.openstack.org/tc/reference/runtimes/zed.html Change-Id: Iba5074ea6f981a7527e86cfc98edd1ed7dd3086f
* Merge "Move FIPS jobs to experimental and periodic queue"Zuul2022-03-291-3/+6
|\
| * Move FIPS jobs to experimental and periodic queueafariasa2022-03-141-3/+6
| | | | | | | | Change-Id: Id8d29ac00102c958ddc6f8d0c217fb11282a7d08
* | Merge "Add Python3 zed unit tests"Zuul2022-03-191-2/+2
|\ \
| * | Add Python3 zed unit testsOpenStack Release Bot2022-03-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for zed. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Ia141d43de268b1153b157b1adccb111955f36fd6
* | | Merge "Attempt to thin out nova-ceph-multistore"Zuul2022-03-151-0/+9
|\ \ \ | |_|/ |/| |
| * | Attempt to thin out nova-ceph-multistoreDan Smith2022-03-141-0/+9
| |/ | | | | | | | | | | | | | | | | This job is pretty heavy and has been triggering OOMs that take out mysqld lately. This disables swift (and c-bak as a result) to try to reduce the runtime footprint. Losing coverage of these services should not be a problem for the goal of this job. Change-Id: Icc18ddd847465069aea34b226851afaeb94594fc
* | Changes Emulation CI to weekly-periodicJonathan Race2022-03-101-1/+5
|/ | | | | | | | | | | Due to initial release of emulated architecture feature the CI has been changed to run less frequent to save CI hours. This will be revisited in later releases as feature gains greater support and capabilities. Implements: blueprint pick-guest-arch-based-on-host-arch-in-libvirt-driver Signed-off-by: Jonathan Race <jrace@augusta.edu> Change-Id: I7b085c2086a720a049c9b04a6ff10a0e5cc9d650
* Merge "Add grenade-skip-level irrelevant-files config"Zuul2022-03-071-0/+2
|\
| * Add grenade-skip-level irrelevant-files configDan Smith2022-03-021-0/+2
| | | | | | | | | | Change-Id: I28218488e3aa9bc906c4d699ebec8fa35f302ade Depends-On: https://review.opendev.org/c/openstack/tempest/+/830670
* | Merge "Enable unified limits in the nova-next job"Zuul2022-03-051-0/+3
|\ \ | |/ |/|
| * Enable unified limits in the nova-next jobmelanie witt2022-03-041-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This configures the nova-next job to enable the new experimental unified limits functionality. This also adds basic testing for nova "global" limits in keystone in the post-test-hook for the nova-next job. These can't be tested in tempest because they involve modifying global quota limits that would affect any other server tests running in parallel. Related to blueprint unified-limits-nova Depends-On: https://review.opendev.org/c/openstack/devstack/+/789962 Depends-On: https://review.opendev.org/c/openstack/tempest/+/790186 Depends-On: https://review.opendev.org/c/openstack/tempest/+/804311 Change-Id: I624b2684867305a9095e8964ead786c7b0c28242
* | zuul-job for Adds Pick guest CPU architecture based on host archJonathan Race2022-02-251-20/+62
|/ | | | | | | | | | | | in libvirt driver support This is split 3 of 3 for the architecture emulation feature. Added initial ci content for tempest test. Implements: blueprint pick-guest-arch-based-on-host-arch-in-libvirt-driver Signed-off-by: Jonathan Race <jrace@augusta.edu> Change-Id: I0159baa99ccf1e76040c197becf2a56c3d69d026
* Merge "nova-next: Drop NOVA_USE_SERVICE_TOKEN from subnode"Zuul2022-02-211-1/+0
|\
| * nova-next: Drop NOVA_USE_SERVICE_TOKEN from subnodeLee Yarwood2021-12-031-1/+0
| | | | | | | | | | | | | | I68f7b7e78cc8a7f22f3e495b1b20a311dacff6c5 missed this when removing it from the controller. Change-Id: Ibc9dea963dc1f9683bd47da7e1bd8d0241176211
* | Merge "skip test_tagged_attachment in nova-next"Zuul2022-02-051-1/+1
|\ \
| * | skip test_tagged_attachment in nova-nextSean Mooney2022-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds tempest.api.compute.servers.test_device_tagging.TaggedAttachmentsTest.test_tagged_attachment to the tempest exclude regex over the past few weeks we have noticed this test failing intermitently and it has not started to become a gate blocker. This test is executed in other jobs that use the PC machine type and is only failing in the nova-next job which uses q35. As such while we work out how to address this properly we skip it in the nova-next. Change-Id: I845ca5989a8ad84d7c04971316fd892cd29cfe1f Related-Bug: #1959899
* | | Revert "Revert resize: wait for events according to hybrid plug"Artom Lifshitz2022-01-311-2/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 7a7a223602ca5aa0aca8f65a6ab143f1d8f8ec1b. That commit was added because - tl'dr - upon revert resize, Neutron with the OVS backend and the iptables security group driver would send us the network-vif-plugged event as soon as we updated the port binding. That behaviour has changed with commit 66c7f00e1d9. With that commit, we started unplugging the vifs on the source compute host when doing a resize. When reverting the resize, the vifs had to be re-plugged again, regarldess of the networking backend in use. This renders commit 7a7a223602ca5aa0aca8f65a6ab143f1d8f8ec1b. pointless, and it can be reverted. Conflicts - most have to do with context around this commit's code: nova/compute/manager.py a2984b647a4 added provider_mappings to _finish_revert_resize_network_migrate_finish()'s signature 750aef54b19 started using _finish_revert_resize_network_migrate_finish() in _finish_revert_snapshot_based_resize_at_source() nova/network/model.py 8b33ac06445 added get_live_migration_plug_time_events() and has_live_migration_plug_time_event() 7da94440db1 added has_port_with_allocation() nova/objects/migration.py f203da38387 added is_resize() and is_live_migration() nova/tests/unit/compute/test_compute.py a0e60feb3ec added request_spec to the test nova/tests/unit/compute/test_compute_mgr.py be278006a58 added unit tests below ours nova/tests/unit/network/test_network_info.py 7da94440db1 (again) added tests for has_port_with_allocation() nova/tests/unit/virt/libvirt/test_driver.py and nova/virt/libvirt/driver.py are different in that attempting to identify individual conflicts is a pointless exercise, as so much has changed (mdev, vtmp, the recent wait for events during hard reboot workaround config option, etc). They can be treated as manual removal of any code that had to do with the bind-time events logic (though guided by the conflict markers in git). TODO(artom) There was a follow up commit, 78a08d44ea68b31e27ce344f452756886ad309bd, that added the migration parameter to finish_revert_migration(). This is no longer needed, as the migration was only used to obtain plug-time events. We'll have to undo that as well. Closes-bug: 1952003 Change-Id: I3cb39a9ec2c260f422b3c48122b9db512cdd799b
* | Add nova-ovs-hybrid-plug jobArtom Lifshitz2022-01-311-0/+62
| | | | | | | | | | | | | | | | | | | | | | We have a gap in our testing of the exernal events interaction between Nova and Neutron. The nova-next job tests with the OVS network backend, and Neutron has jobs that test the OVN network backend, but nothing tests OVS + the iptables security group firewall driver, aka "hybrid plug". Add a job to test that. Related-bug: 1952003 Change-Id: Ie42eaa2a39ef097b0eb69b8863bb342bae007fff
* | Merge "Add check job for FIPS"Zuul2022-01-251-0/+3
|\ \
View Lorry Controller Status