openEuler 20.03-LTS-SP2 was out of date in May 2022. 22.03 LTS
is the newest LTS version. It was release in March 2022 and
will be maintained for 2 years. This patch upgrades the LTS
version. It'll be used in Devstack, Kolla-ansible and so on
in CI jobs.
Recent changes in how nodepool deletes images mean that we need
a list of all diskimages on every builder (otherwise there is a
small window where a new image build might be deleted by a different
builder). To correct this, list all diskimages on all builders
(but they still won't build images they shouldn't because they have
different provider configurations).
This is a partial revert of . For the bootstrap we only use the
release pocket, not updates or security, so the version of
ca-certificates we install initially is too old to verify current
LetsEncrypt protected hosts.
We have noticed Jammy jobs failing with DISK_FULL returns from Zuul.
Upon further investigation, they have hundreds of megabytes of syslog
filled with traces. As noted inline we've debugged this down to SSBD
interactions with some cloud providers.
Set this to the later-kernel upstream default of "prctl" to avoid this
Debian is already doing this and according to ubuntu package search
apt-transport-https is a transitional package at least as far back as
bionic. We leave xenial with http as it isn't clear if apt there
Once we've settled on a max-servers value of 0 without any servers this
is the nextstep in removing the provider. This should completely remove
the provider from the launcher and the image builders.
We keep the airship-citycloud nodepool provider for historical
information purposes. We can clean this up later.
We've been notified that these resources won't be provided any longer.
This is the first step of setting max-servers to 0 and removing images
from the cloud. Once that is in we can remove the cloud more completely.
This distro release reached its EOL December 31, 2021. We are removing
it from our CI system as people should really stop testing on it. They
can use CentOS 8 Stream or other alternatives instead.
In line with CentOS deprecation, http://mirrorlist.centos.org has
stopped returning mirror sources. As the dib builds have this in the
initial image clones, they won't build any more. Pause this to stop a
spiral of failing builds.
Since we setup local mirrors, things might keep working in our
ecosystem for a bit, so far the upstream mirrors haven't pulled the 8/
directory directly it seems.
This removes the label, nodes, and images for opensuse-tumbleweed across
our cloud providers. We also update grafana to stop graphing stats for
The openEuler node can be setup successful now. While the
error `/opt/cache/files, No such file or directory ` will
raise when running devstack jobs on it.
This patch add the cache-devstack element for openEuler diskimage
to ensure devstack jobs work well.
Change I20e1a926d02a632450b8114d84a0fa738b7ec639 updated this for
the arm64 images, but we have amd64 images as well which will need
the same treatment.
DIB's tests suggest these images should build successfully again, so
let's see if we can get them to build and launch reachable nodes in
Apparently Gentoo carries Python 3.9 now, so set that as well.
Fedora-34 was paused until bug fixes could land in DIB and our nodepool
builder images could be updated. This happened about 2 weeks ago from
what I can tell so unpause and let those images build again.
Opensuse-15 was paused becuase the images failed to build. Unfortunately
that was almost a year ago and we don't have logs for why this was
broken. Unpause to generate new logs allowing us to debug them.
We are having issues talking to https://image.api.mtl01.cloud.iweb.com
as it appears to be missing an intermediate certificate.
This has been reported to the provider (Ticket #4526047)
In the mean time, disable uploads, which are in a failure loop.
LE recently expired it's root certificate. Unfortunately, the base
Ubuntu distros (up to focal) use a 2019 ca-certificates package that
hasn't accounted for this. Even more unfortunately, deboostrap can't
use the updates repo to get a more recent certificate package when
building the initial chroot.
The end result is that the chroot can't contact the mirrors via https
to actually pull the updated certificates package from them, breaking
To work around this use http:// for the mirror location.
This is the next step in cleaning up the inap provider. We set empty
resources lists in nodepool config for the inap provider so that
nodepool will automatically clean up after itself.
This varaible makes it's way through to zuul and the
``ansible_python_interpreter`` variable in the inventory. It seems
that autodetection on Bullseye currently tries to choose python2, so
this will override it.
This adds the new inmotion cloud to nodepool. We will upload images then
use a max server count of 8. There is potential to grow this number if
we can run an executor in this cloud that can hit node private addresses
or if we can get IPv6.
Since Debian Buster can not be used with nova 23.0.0 because of the
min required libvirt version, we should make Bullseye available for CI
to ensure that OpenStack Wallaby release will run on it smoothly.