summaryrefslogtreecommitdiff
path: root/zuul.d/ironic-jobs.yaml
Commit message (Collapse)AuthorAgeFilesLines
* [CI] Swap anaconda urlsJulia Kreger2023-01-261-3/+3
| | | | | | | | The anaconda job is failing as were getting a redirect issued back upon attempting to validate URLs. The servers are now directing us to use HTTPS instead. Change-Id: Iac8e6e58653ac616250f4ce3ab3ae7f5164e5b03
* Merge "CI: Reset VM footprint to 2.6GB"Zuul2023-01-111-1/+1
|\
| * CI: Reset VM footprint to 2.6GBJulia Kreger2023-01-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | This commit partially reverts change set I0bfef09a5312a17be54ce5c09805f06b7c349026 where the amount of memory for test VMs was increased to 4GB. This was because excess junk getting stuck in the staged ramdisk images used by CI. Change-Id: Ia0c74cbeecdb9febf9f7a4e76db84e0f378a97fc
* | Use centos grub artifacts with centos ramdisk for vmediaJulia Kreger2023-01-031-0/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It appears we are getting an opcode error when attempting to boot Centos 9-stream utilizing the EFI artifacts from Ubuntu. Technically this should work, however further aftifacts in the boot chain may be signed with other key credentials that Ubuntu's grub does not know about, because the chain of trust is MSFT -> Vendor shim (slow change rate) -> Vendor GRUB -> Kernel Where vendor differences should never work, is if Secure Boot is enforcing. Exception on launch: X64 Exception Type - 06(#UD - Invalid Opcode) CPU Apic ID - 00000000 !!!! A similar Debian bug is open for a very similar issue: https://groups.google.com/g/linux.debian.bugs.dist/c/BOiLLeROrmo However, no additional comments or information have been in follow up to that reported issue. So in the mean time, we're going to try and do what those smarter than I recommend, use the vendor's binaries for their distribution. There is one further, potentially far more depressing possibility, that centos9's kernel doesn't support the type of hardware we're getting. This is suggested by the precise opcode error, UD, https://xem.github.io/minix86/manual/intel-x86-and-64-manual-vol3/o_fe12b1e2a880e0ce-212.html But again, easiest possibility first. Change-Id: Id9bd30bc3c2f1076555317e4a3f277725fa7c1f4
* Fix CIRiccardo Pittau2022-12-291-2/+1
| | | | | | | | | | | - Remove skipsdist that it was never supported and causes breakage when used with usedevelop. - add script to allowlist for pep8 test - disable setuptools autodiscovery - Increase base VM memory according to new requirements for CS9 based IPA Change-Id: I0bfef09a5312a17be54ce5c09805f06b7c349026
* Ironic doesn't use metering; don't start it in CIJay Faulkner2022-12-131-1/+0
| | | | | | | We don't use metering. We do use every byte of ram we can get our hands on. Change-Id: I839c7fd4cb6fe8661a25e6b4e00650575ae17520
* [grenade] Explicitly enable Neutron ML2/OVS services in the CI jobSławek Kapłoński2022-12-091-0/+13
| | | | | | | | | | | | | As with [1] basic grenade job will be switched to run with OVN as Neutron backend, which is default in Devstack, we need to explicitly disable ML2/OVN neutron services in the ironic-grenade job and use ML2/OVS related services in that job. Depends-On: https://review.opendev.org/c/openstack/devstack/+/867065 [1] https://review.opendev.org/c/openstack/grenade/+/862475 Change-Id: I2ef96d1b3e19004f05253dfae508e9f07ae58f63
* Cross test sushy with python 3.10Riccardo Pittau2022-10-201-2/+4
| | | | | | We don't test python 3.8 anymore in antelope Change-Id: I4748f14f7a75ae9da204ffafb61c8e495822f040
* CI: Changes to support Anaconda CI jobsJulia Kreger2022-09-061-0/+42
| | | | | | | | | | | Introduces additional job configuration to enable automated integration testing via tempest of the anaconda deployment interface. Also, configures a private subnet with DNS, which is required by anaconda executing, in order to facilitate processing of URLs. Change-Id: I61b5205cf2c9f83dfcabf4314247c76fb6a56acd
* Finally remove support for netboot and the boot_option capabilityDmitry Tantsur2022-08-021-13/+0
| | | | | | | | | | | Instance network boot (not to be confused with ramdisk, iSCSI or anaconda deploy methods) is insecure, underused and difficult to maintain. This change removes a lot of related code from Ironic. The so called "netboot fallback" is still supported for legacy boot when boot device management is not available or is unreliable. Change-Id: Ia8510e4acac6dec0a1e4f5cb0e07008548a00c52
* CI: Pull in diskimage-builder until new release is cutJulia Kreger2022-06-301-0/+2
| | | | Change-Id: I88a4863cd24258eb0b395303738c23e3468615c0
* Merge "Remove netboot jobs from the gate"Zuul2022-06-251-25/+19
|\
| * Remove netboot jobs from the gateDmitry Tantsur2022-05-311-25/+19
| | | | | | | | | | | | | | Netboot option will be removed soon, this change stops covering it. Some jobs have been renamed to reflect the new reality. Change-Id: I7e248c3deb4778fcf59bc64821833987653fbbcd
* | devstack: use CentOS 9 for DIB IPA buildsDmitry Tantsur2022-05-251-1/+1
|/ | | | | | | | | | | Additionally bumps CPU model to host-model as centos9 builds now require a subset of CPU processors which include advanced features. Host-model also allows for the VM to still start when running with pure qemu, as opposed to KVM passthrough. https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level#architectural_considerations_for_rhel_9 Change-Id: Ic261efd4bf6f5929687df5e7b1b51b541554af18
* Merge "Fix names of two jobs"Zuul2022-05-091-3/+3
|\
| * Fix names of two jobsRiccardo Pittau2022-04-201-3/+3
| | | | | | | | | | | | | | | | | | | | | | Making jobs names less misleading This should impact sushy and sushy-tools only sushy change https://review.opendev.org/c/openstack/sushy/+/838662 sushy-tools change https://review.opendev.org/c/openstack/sushy-tools/+/838664 Change-Id: I83f3ac7ddc0662e32c205cd8ec0fab073aeaec56
* | Fix v6 CI job - Return it to normal non-voting statusJulia Kreger2022-05-041-2/+10
|/ | | | | | | | | | | | | | | | | | | | | | | * Fixes the IPv6 job by utilizing HOST_IPV6 instead of SERVICE_IPV6, as Devstack now automatically wraps SERVICE_IPV6 with brackets as if it is for a URL. * Locks ipv6 job to bios mode. Ubuntu Focal OVMF/EDK2 does not support IPv6 PXE boot by default. * Split from Devstack in terms of IP usage, since full explicit V6 usage is not a thing anymore. 4+6 is the default in devstack and regardless of what we set on the job we see both now used. So we delineate apart our usage for our own sanity. * Reduce VM Interface count for IPv6 in an attempt to eliminate in-kernel routing confusion by two interfaces on the same physical network. * Set IPv6 mode to dhcpv6-stateless due to fun issues in dhcp clients. When we move to UEFI, this will need to be changed to stateful as stateless is not supported in general by OVMF/E2DK. Once the job has run in normal non-voting for a while, and we ensure that it seems to be stable, we can make it voting again. Change-Id: Ia833bfb64c6c3cc8e48cbe34ed200536652a8adf
* Grenade: Change to use bios because we have funky networkingJulia Kreger2022-04-041-0/+4
| | | | | | | | | | | | | | | | | | Grenade, for some confusing reason, creates a separate network, and uses that for upgrade testing as opposed to the original network the VMs were bound to. If Julia's memory is correct, this was for multinode upgrade testing. Anyway, When in UEFI mode, it appears that the TFTP packets don't get tracked nor cross the boundrary. We likley need to explicitly address this, but first, lets get the job working as it was and can then update it. Also, update requirements because markupsafe removed soft_unicode method taht was deprecated since a while. Jinja2 started using the new soft_str method since version 3.0.0 Change-Id: Iaebe966569962b0d3d43774d57b570469479f159
* Deprecate instance network bootDmitry Tantsur2022-02-231-1/+1
| | | | | | | It's insecure and not very popular. See this post for details: http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026224.html Change-Id: I9a2df47bb8c08cc991b3c615a9eb533aba3171f4
* CI: force config drive on the multinode job's subnodeDmitry Tantsur2022-02-211-0/+1
| | | | | | | We need configdrives to pass information reliably, and the new cirros image does not work without them. Change-Id: I6cafa050d5c1c8289483f968d26c50485fd4528a
* Merge "CI: use a custom cirros partition image instead of the default"Zuul2022-02-161-5/+1
|\
| * CI: use a custom cirros partition image instead of the defaultDmitry Tantsur2022-02-161-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cirros partition images are not compatible with local boot since they don't ship grub (nor a normal root partition). This change adds a script that builds a partition image with UEFI artifacts present. It still cannot be booted in legacy mode, but it's a progress. Set the tempest plugin's partition_netboot option. We need it to inform the tempest plugin about the ability to do local boot. This option already exists but is never set. Also set the new default_boot_option parameter, which will be introduced and used in Iaba563a2ecbca029889bc6894b2a7f0754d27b88. Remove netboot from most of the UEFI jobs. Change-Id: I15189e7f5928126c6b336b1416ce6408a4950062
* | Clean up jobs with legacy namesDmitry Tantsur2022-02-031-5/+5
|/ | | | | | | | | | Not everyone on the team even knows what pxe_ipmitool used to mean :) Furthermore, we don't need "ipa" in job names, everything uses IPA for... even longer than pxe_ipmitool does not exist. While here, one job was clearly meant to use BIOS boot, but it does not. Change-Id: I8a37efa0f222361f30ddb7fa621548685a40f961
* Merge "CI: reduce api worker processes to 1"Zuul2021-12-121-0/+4
|\
| * CI: reduce api worker processes to 1Julia Kreger2021-12-081-0/+4
| | | | | | | | | | | | | | | | | | | | | | CI is memory intensive, and we realistically don't need 2 or more API workers running for every single WSGI process which does not implement it's own specific override value. This should reduce the memory footprint by an average of six processes which consume 60-90 MB each. Change-Id: Ia0a986152c2b9fc9c5ff54cf698a351db452fbbd
* | CI: Lower test VM memory by 200MB19.0.0Julia Kreger2021-12-081-1/+1
|/ | | | | | We're seeing OOM events in CI, hopefully this helps. Change-Id: Id8c0e4830011ca2fa526df461ed5b9b01f769cf9
* devstack: provide a default for OS_CLOUDDmitry Tantsur2021-12-081-12/+0
| | | | | | Not having it breaks the inspector grenade job. Change-Id: I7ee28a85cb2005dd69e6711b301cd029b8ca40cc
* Add a unit test job with Sushy from sourceDmitry Tantsur2021-11-251-0/+24
| | | | | | | The final goal is to run it on sushy itself to make sure there are no regressions. Change-Id: I6f4bee9a3fa439b1477c41c82304652a801ea55e
* CI: Fix devstack plugin with RBAC changesJulia Kreger2021-11-191-0/+12
| | | | | | | | | | | | | | | | | | | | Changes a neutron call to be project scoped as system scoped can't create a resource and, and removes the unset which no longer makes sense now that I86ffa9cd52454f1c1c72d29b3a0e0caa3e44b829 has merged removing the legacy vars from devstack. Also renames intenral use setting of OS_CLOUD to IRONIC_OS_CLOUD as some services were still working with system scope or some sort of mixed state occuring previously as some of the environment variables were present still, however they have been removed from devstack. This change *does* explicitly set an OS_CLOUD variable as well on the base ironic job. This is because things like grenade for Xena will expect the variable to be present. Depends-On: https://review.opendev.org/c/openstack/devstack/+/818449 Change-Id: I912527d7396a9c6d8ee7e90f0c3fd84461d443c1
* Yoga: Change default boot mode to uefiJulia Kreger2021-10-041-11/+27
| | | | | | | | Change the default boot mode to UEFI, as discussed during the end of the Wallaby release cycle and previously agreed a very long time ago by the Ironic community. Change-Id: I6d735604d56d1687f42d0573a2eed765cbb08aec
* Disable Neutron firewallJulia Kreger2021-09-201-0/+5
| | | | | | | | | | | | | | | Neutron's firewall initialization with OVS seems to be the source of our pain with ports not being found by ironic jobs. This is because firewall startup errors crashes out the agent with a RuntimeError while it is deep in it's initial __init__ sequence. This ultimately seems to be rooted with communication with OVS itself, but perhaps the easiest solution is to just disable the firewall.... Related: https://bugs.launchpad.net/neutron/+bug/1944201 Change-Id: I303989a825a7e35f1cb7b401134fd63553f6791c
* Dial back gate job memory allocationJulia Kreger2021-09-151-1/+1
| | | | | | | | | | | | | | | | | Observed an OOM incident causing ironic-tempest-ipa-partition-pxe_ipmitool to fail. One vm started, the other seemed to try to start twice, but both times stopped shortly into the run and the base OS had recorded in it an OOM failure. It appears the actual QEMU memory footprint being consumed when configured at 3GB is upwards of 4GB, which obviously is too big to fit in our 8GB VM instance. Dialing back slightly, in hopes it stabilizes the job. Change-Id: Id8cef722ed305e96d89b9960a8f60f751f900221
* Set postgresql password encryption for FIPS complianceSteve Baker2021-08-051-1/+0
| | | | | | | This is part of the work to add jobs which confirm ironic works with FIPS enabled, but this change is also appropriate non-FIPS jobs. Change-Id: I4af4e811104088d28d7be6df53c26e72db039e08
* Merge "Scoped RBAC Devstack Plugin support"Zuul2021-07-211-0/+22
|\
| * Scoped RBAC Devstack Plugin supportJulia Kreger2021-07-151-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds support to the ironic devstack plugin to configure ironic to be used in a scope-enforcing mode in line with the Secure RBAC effort. This change also defines two new integration jobs *and* changes one of the existing integration. In these cases, we're testing functional crub interactions, integration with nova, and integration with ironic-inspector. As other services come online with their plugins and devstack code being able to set the appropriate scope enforcement configuration, we will be able to change the overall operating default for all of ironic's jobs and exclude the differences. This effort identified issues in ironic-tempest-plugin, tempest, devstack, and required plugin support in ironic-inspector as well, and is ultimately required to ensure we do not break the Secure RBAC. Luckilly, it all works. Change-Id: Ic40e47cb11a6b6e9915efcb12e7912861f25cae7
* | Set glance limit for baremetal friendly imagesJulia Kreger2021-07-191-0/+4
|/ | | | | | | | | | | | | The devstack default limit enforcement for glance defaults to 1GB, and unfortunately this is too small for many to use larger images such as centos which includes hardware firmware images for execution on baremetal where drivers need the vendor blobs in order to load/run. Sets ironic-base to 5GB, and updates examples accordingly. Depends-On: https://review.opendev.org/c/openstack/devstack/+/801309 Change-Id: I41294eb571d07a270a69e5b816cdbad530749a94
* Don't run the inspector job on changes to inspector testsDmitry Tantsur2021-06-171-0/+16
| | | | | | | The current irrelevant-files contains the ironic tests directory, but not the inspector one. Change-Id: I1654e1333f95d4c3ffd25daa2b80ae4cf1033d91
* Merge "CI: Collect a snapshot of network connections"Zuul2021-05-251-1/+1
|\
| * CI: Collect a snapshot of network connectionsJulia Kreger2021-01-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A recent magnum bug (https://storyboard.openstack.org/#!/story/2008494) when running with uwsgi has yielded an interesting question if Ironic is orphaning rpc clients or not. Ironic's code is slightly different but also very similar, and similar bugs have been observed in the past where the python garbage collection never cleans up the old connection objects and effectively orphans the connection. So we should likely at least try to collect some of the information so we can determine if this is the case in our CI jobs. Hence this change and attempt to collect that data after running CI. Change-Id: I4e80c56449c0b3d07b160ae6c933a7a16c63c5c5
* | Stop testing the iscsi deploy interfaceDmitry Tantsur2021-04-301-4/+4
| | | | | | | | Change-Id: If876d5bbb7e18f293673d56912ecab3170fe5dfb
* | Enable Reuse of Zuul Job in 3rd Party CI EnvironmentVanou Ishii2021-03-171-32/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At current Zuul job in zuul.d/ironic-jobs.yaml, items of required-project are like this (without leading hostname) required-projects: - openstack/ironic - openstack/ABCD but not like this (with leading hostname) required-projects: - opendev.org/openstack/ironic - opendev.org/openstack/ABCD With first format, if we have two openstack/ironic entries in Zuul's tenant configuration file (Zuul tenant config file in 3rd party CI environment usually has 2 entries: one to fetch upstream code, another for Gerrit event stream to trigger Zuul job), we'll have warning in zuul-scheduler's log Project name 'openstack/ironic' is ambiguous, please fully qualify the project with a hostname With second format, that warning doesn't appear. And Zuul running at 3rd party CI environment can reuse Zuul jobs in zuul.d/ironic-jobs.yaml in their Zuul jobs. This commit modifies all Zuul jobs in zuul.d/ironic-jobs.yaml to use second format. Story: 2008724 Task: 42068 Change-Id: I85adf3c8b3deaf0d1b2d58dcd82724c7e412e2db
* | Prepare to use tinycore 12 for tinyipaRiccardo Pittau2021-03-021-8/+8
| | | | | | | | | | | | Tinycore 12 requires some more RAM than its predecessor. Change-Id: Ibced843f34c78af7780bfe1ade833208b458bb8b
* | Enable swift temporary URLs in grenade and provide a good error messageDmitry Tantsur2021-02-241-0/+2
| | | | | | | | | | | | The fixed configdrive_use_object_store requires them. Change-Id: Ie7323ae107c7f801be010353c7c4f3b8a43c3a1a
* | Switch multinode jobs to 512M RAMDmitry Tantsur2021-02-151-2/+2
|/ | | | | | 384M no longer works reliably with newer tinyIPA. Change-Id: I7e48b2e682dc0d5e6109e17b0e73ee9763a29d23
* CI: switch the multinode job to tempest-multinode-full-baseDmitry Tantsur2020-12-141-1/+2
| | | | | | | | | | The non-base job is designed for the integrated gate and may have unnecessary side effects. It has recently overriding the OVS agent bridge settings, breaking our job. Make the job voting again. Change-Id: Ied8cafd32c3e634d498467ebe878a411f0b24e6d
* Use openstack-tox for ironic-tox-unit-with-driver-libsRiccardo Pittau2020-11-271-1/+1
| | | | | | | All the tox jobs are based on openstack-tox, we should convert ironic-tox-unit-with-driver-libs too. Change-Id: I20836d586edccfb8cd8fed1f3a89f1497ff96943
* Convert last bionic jobs to focalRiccardo Pittau2020-11-121-22/+3
| | | | | | And disable dstat in ironic-base for the time being. Change-Id: Ib05a952260d027f9f1307a9948ac5691b57e96d3
* CI: increase cleaning timeout and tie it to PXE boot timeoutDmitry Tantsur2020-10-271-1/+0
| | | | | | | | | | We're seeing cases where cleaning barely manages to finish after a 2nd PXE retry, failing a job. Also make the PXE retry timeout consistent between the CI and local devstack installations. Change-Id: I6dc7a91d1a482008cf4ec855a60a95ec0a1abe28
* migrate testing to ubuntu focalRiccardo Pittau2020-10-051-3/+19
| | | | | | | | | | | | | | As per victoria cycle testing runtime and community goal we need to migrate upstream CI/CD to Ubuntu Focal(20.04). keeping few jobs running on bionic nodeset till https://storyboard.openstack.org/#!/story/2008185 is fixed otherwise base devstack jobs switching to Focal will block the gate. Change-Id: I1106c5c2b400e7db899959550eb1dc92577b319d Story: #2007865 Task: #40188
* Merge "Deprecate the iscsi deploy interface"Zuul2020-09-241-11/+2
|\
View Lorry Controller Status