From 5d4541e1e306c4bbbe467a6ef75e40c2b397f2f4 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Fri, 8 Aug 2025 06:01:56 -0700 Subject: [PATCH] ci: move metal3 job to larger memory node The meteal3 job has traditionally operated as a very tight memory condition for quite some time. Specifically running minikube, ironic, and two VMs in 8 GB of memory also influenced the job design. However, with the removal of eventlet, this memory footprint and process model swells a little bit creating conditions where the job is essentially guarenteed to fail. Further discussion with Riccardo, one of the other Ironic/Metal3 contributros yielded that they were already thinking of increasing the size of the VM because they had been encountering memory issues. Given that this job already runs lean, albeit with no swap which is intentional to prevent disk IO generated noisey neighbor conditions, the only real choice is to just increase the VM size to the next realistic size in OpenDev CI. Change-Id: I87f9c94e6585347d8a35a1d04dd7d101a9e68261 Signed-off-by: Julia Kreger --- zuul.d/metal3-jobs.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zuul.d/metal3-jobs.yaml b/zuul.d/metal3-jobs.yaml index dbb06bfda1..34c0e9cc2f 100644 --- a/zuul.d/metal3-jobs.yaml +++ b/zuul.d/metal3-jobs.yaml @@ -3,7 +3,7 @@ name: metal3-base abstract: true description: Base job for metal3-dev-env based ironic jobs. - nodeset: openstack-single-node-noble + nodeset: ironic-single-node-noble run: playbooks/metal3-ci/run.yaml post-run: playbooks/metal3-ci/post.yaml timeout: 5400