- May 06, 2024
-
- May 01, 2024
-
-
Julia Kreger authored
The drivers were removed a very very long time ago in a galaxy far away. It no longer makes sense to keep them in the tempest plugin. Change-Id: Iadac0a41caea8bdbac9aedae83170eb81c331a05
-
Zuul authored
-
- Apr 30, 2024
-
-
Takashi Kajinami authored
These are detected as errors since the clean up was done[1] in the requirements repository. [1] 314734e938f107cbd5ebcc7af4d9167c11347406 Change-Id: Ib566620c744a912400a4dbd9c019d92d3a337b90
-
- Apr 29, 2024
-
-
Zuul authored
-
- Apr 23, 2024
-
-
Zuul authored
-
- Apr 19, 2024
-
-
Julia Kreger authored
Change-Id: Ieb221bd16fb9ba37f2b205dcaea3de3c201d0f03
-
Julia Kreger authored
And remove an invalid test at this point, and fix versioning tests. TL;DR is we didn't run the vif tests for... a very long time, and I got a report they were failing downstream. In fixing them, since they were semi-reliant upon specific behavior, I also broke some other tests, and had to content with legacy behaivor being tested by the plugin which had to be navigated slightly differently, such as today some tests needed the fake deploy interface, and the noop network interface to properly execute in a non-blocking fashion. Change-Id: I285c813c09eece538e66b43107825684f4681d5f
-
- Apr 18, 2024
- Apr 04, 2024
-
-
Julia Kreger authored
The boot_iso ramdisk test unfortunately has been discovered to orphan occupied "nodes" after the test has executed. This change triggers the test to send a command to force the node to be unprovisioned at the end of the test. Closes-Bug: 2055469 Change-Id: Ib525fe099d5884f442cdc375c5a8d230710d20a4
-
- Apr 03, 2024
-
-
Julia Kreger authored
Previously, the tempest plugin would orphan a CUSTOM_RAID deploy template in the ironic deployment by not removing it after the test has been completed. This change adds a cleanup to trigger the deletion of the template, so the test does not fail upon a second re-execution against the environment. Closes-Bug: 2055456 Change-Id: I21ea329feb48e56b7f2984f62cdbc41c1a0bd1d0
-
- Mar 29, 2024
-
-
Julia Kreger authored
Tempest plugins are... weird. The challenge is to have a branchless utility which can be loaded and help provide feedback if the remote service is correctly responding as we would expect. This works great in theory, until you have to either do some sort of negative test, or plan in advance, or until you have some sort of mixed state environment. This also weirdly restraints testing against older versions on older branches, requiring further care and feeding to keep things passing. And the way issues like these are resolved, originally, was to leverage manual human configuration. The problem is, that doesn't always work and operationally becomes an increased burden. So the logical path forward is for the plugin to automatically skip specific tests *based upon* the remote offered API microversion, much like many of the tests do if a driver or running configuration does not exist. This can be done because when we compose tests, we have a minimum and maximum API version where we know the test is valid, and if the remote endpoint is outside of that bound. The result is now the plugin will query the remote endpoint and collect the minimum and maximum API versions as part of skip version testing, so if either are defined on a test class, then we make a decision automatically removing the need to configure aspects specifically. Change-Id: I197e6c30c8514e1f72cb1ce3ebad851802632203
-
- Mar 06, 2024
-
-
Julia Kreger authored
So it turns out as highlighted by looking at bug 2054722 that you can end up creating nodes with "fake" hardware nodes in the default config we test in the gate, which end up with "fake" as the deploy_interface, but if you try to run the same test against a production configured ironic deployment, it fails because it likely ends up with a default of "agent" as the deploy_interface. Unfortunately, a review of test logs also reveals that the same basic problem exists with the network_interface field *as well*, where tests were written expecting the default to be a fake or noop interface out of the box. Note: This depends-on is to be removed before mering, it is enable additional issues to be identified. Change-Id: Id0051d9b39bc0f46e3afee5bbfa8a2062114df80
-
- Feb 12, 2024
-
-
Julia Kreger authored
The idea here came out of the 2024.1 PTG held in ?October? 2023, with the goal of being able to exercise testing of boot interfaces as a group in a single job, instead of spreading it out amongst CI jobs with different scenarios. That doesn't mean different scenarios are wrong, but as we add more boot interfaces as part of supporting HTTPBoot, we cannot double our scenarios. In theory, the hope is we should be able to consolidate down several secenario jobs into just one test running these jobs. Change-Id: Id41ee40c36624387216b2cfc1501f01a3217b2af
-
- Feb 08, 2024
-
-
Jay Faulkner authored
Validates: - Unfiltered requests get sharded nodes - Filtering by a single shard - Filtering by >1 shards - Filtering by sharded nodes - Filtering by unsharded nodes Change-Id: Id37e8d6db098bb8decae87b6184bab4482321316
-
- Jan 24, 2024
-
-
Julia Kreger authored
Back after we added the new policies, at some point we should have changed the default state for the tempest tests so they assume/default to the understanding that Ironic is enforcing scope and to use the appropriate client when launching tests, because Ironic restructed it's access model to better align with the overall community and further enable infrastructure operators. Closes-Bug: 2051137 Change-Id: I564af48698d20a150699933bf7e2e829b104ab04
- Jan 21, 2024
-
-
Kyrylo Romanenko authored
Add tests: test_vif_already_attached_on_internal_info test_vif_already_attached_with_portgroups test_vif_attach_no_free_port test_vif_attach_no_port test_vif_attach_with_empty_portgroup test_vif_attach_port_not_in_portgroup test_vif_attach_node_doesnt_exist test_vif_attach_no_args test_vif_detach_not_existing test_vif_detach_no_args Closes-Bug: #1666534 Change-Id: I657fbecd37ceec424da6182507f324b653288857
-
- Dec 05, 2023
- Nov 17, 2023
-
-
Julia Kreger authored
Change-Id: I3e3849a9aefcc568dd39f3765d6b8e8784b2771a
-
- Nov 03, 2023
-
-
Julia Kreger authored
Creating test to help facilitate the fix of bug 2032377 and ultimately help ensure we have a backwards compatible fix. The scenario: * Creates a shiny new network without dhcp, and adds a router. * Sets that network as the provisioning network for the node. * Creates a port on that network, assigns that port as the VIF. * Creates a configuration drive network_data.json file payload * Triggers deployment, utilizing the aformentioned network_data payload and configuration drive. * Once deployment has complete, attempts to ping the remote host. * Once pingable, and this is configurable, it will then attempt to rebuild the remote host, basically forcing the condition covered in bug #2032377. * Rebuild is completed, and the host is attempted to be pinged, again. To facilitate this, three configuration options have been added. Two are external network settings. Because there is no way in a devstack configuration of neutron to advertise the next hop router, we have to have a pre-assigned/configured IP on the external network we can attach a router to. We also need to know the external network ID. Then there is basically a option flag if we wish to exercise the pattern for bug 2032377. Ideally, this would be always, but with the complexity and fact a non-stock IPA image is required, one sort of needs to know and then configure as appropriate. Change-Id: Ic848b8051e4d863f30d47c833d334afc879e4f20
-
Julia Kreger authored
Increment the jobs, in other words: * Add jobs for 2023.2 * Mark Zed jobs non-voting * Remove older jobs from the tempest plugin's normal execution as they were non-voting previously. Change-Id: I27d852063a74938992c5cd37e45bfecf31aadd41
-
- Aug 08, 2023
-
-
wangjiaqi07 authored
This repo is now testing only with Python 3, so let's make a few cleanups: - Remove python 2.7 stanza from setup.py Change-Id: Icd0649557b64ff9694ca444bd1d381bb9317992a
-
- Jun 01, 2023
-
-
Harald Jensås authored
Client vif_attach only return resp - not body. On a system without policies enabled the test fail with too maby values to unpack - which is confusing ... Change-Id: I36bce09c9ffe31364d738809adabe65a3af8443f
-
Julia Kreger authored
Adds configs for Zed, 2023.1, but only runs the job on master branch for now, while we sort out a policy fix needing to be backported in ironic. Gives us some initial feedback and forced testing while we fix the other issues. Change-Id: Ic435368a5840aae8dab26a843bd79e0ae2546639
-
- May 25, 2023
-
-
Zuul authored
-
- May 24, 2023
-
-
Harald Jensås authored
Also disable test_reader_cannot_ipa_heartbeat, will follow up. Depends-On: https://review.opendev.org/882597 Change-Id: I966ae89333b6ad553b6f1398d61bc7d8f8b72c74
-
- May 23, 2023
-
-
Julia Kreger authored
- Create 2023.1 stable jobs - Move yoga jobs to non-voting - Remove wallaby non-voting jobs from being executed. Change-Id: Ie30fd6ac8b208265cd6d56f7e94a69f472b5a7c4
-
- May 09, 2023
-
-
Julia Kreger authored
Also advances the anaconda job to 2023.1, since it fails in a very odd way on Zed, and it looks like I might not have had all of the CI related fixes on Zed. Change-Id: Ib7142d2bfcf0cae84dbc647a5870a2e1d4768e25
-
- May 04, 2023
-
-
Riccardo Pittau authored
Fix the exceptions got from test_reader_cannot_get_indicator_state and test_reader_cannot_ipa_heartbeat. Also get_indicator_state takes only 2 arguments since the get_one() function takes only 2 positional arguments besides self, node_uuid and indicator. Change-Id: I4b5399562ffddb6e603f457aef1423f1fe7ba93e
-
Zuul authored
-
- May 02, 2023
-
-
Julia Kreger authored
Change-Id: I4ae825a09838dae198ff663cfc1e602b10bc7084
-
- Apr 25, 2023
-
-
Zuul authored
-
- Apr 21, 2023
-
-
Jay Faulkner authored
Updated dep to latest hacking - 6.0.0 Change-Id: Ic5f2a98d2368f6a4aa4393ebccaee8c805761ce8
-
- Apr 18, 2023
-
-
Julia Kreger authored
Enforce/test the state of each policy's engagement for baremetal nodes, project reader and system reader. The tests use a try clause, catches the exception and checks the response status code match what is expected. Change-Id: I0b5f8eb881462f5d78f65bd37fbb8b296d9880eb
-
- Mar 03, 2023
-
-
Dmitry Tantsur authored
I have a feeling that class-level logic involving CONF does not work because CONF is populated later. Change-Id: I65c65faf55069a4c9d668e0e0ba06ffc8b6b43ed
-
- Feb 17, 2023
-
-
Zuul authored
-