This is a partial revert of [0]. 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.
[0] I455568f1e261060aefe555e9f5b4ef0830b60157
Change-Id: I673bc0ec687df6db59911f17dae1d50cbc7e3dd6
From Zed cycle onwards, py36 support has been dropped, this
migrate neutron-lib master testing by replacing
openstack-tox-py36-with-neutron-lib-master with
openstack-tox-py39-with-neutron-lib-master
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/842646
Change-Id: Ic10aadbffd76b134e9a546dc1c29ca6116e45a92
The propose-updates job on openstack/requirements was pinned to
ubuntu-bionic so far in order to be able to generate constraints on
python3.6. With [0] the job now needs python3.8 and 3.9, so it should be
running with ubuntu-focal instead.
[0] I663de65a971337fce65a51f0e5a7f959b8da2c03
Change-Id: I9735f34639777c928fbe06febc16dd24667b1405
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
issue.
Change-Id: I09a495a9b50c55b65221be56337f52388a5d9d48
The previous patch[1] applied a partial context to the unbound.log file.
This patch applies a full context to resolve the "partial context" error, using semanage to make the file label persistent.
[1] https://review.opendev.org/c/openstack/project-config/+/841546
Change-Id: Ic15957fa4ef58355efd2e96f143386f393b0a59d
I4f3265c16320613d4ba74a02df1361c5d9cf2fb1 moved this file to
/var/lib/unbound on selinux systems, as it was getting permissions
errors trying to write into /var/log.
This turns out to make it harder to collect the logs from projects
like devstack. It's simpler if we just have the log file in a
consistent place. On selinux systems, set the context, and revert
things to just writing into /usr/log/unbound.log
Change-Id: I6bb58ef0d6bf4cbbb7fd4066e01b7a01d05009c3
Add the jobs for infra-vhd-util-deb (the publish job needs to be here,
we keep the rest just to keep it together).
Change-Id: Ida6e34feb2ca3d7e4bb7a09610aa69dec83b8dc0
Similar to the recent change
Ie00c42857e7a541aa1ccb8fe480756c1e7a38dc4, the patched version of
vhd-util in the openstack-ci PPA produces Xen (rackspace) acceptable
.vhd images from diskimage-builder. This is another tool that isn't
really captured by our gitops model (the need for this is all covered
in [1] as to why this is a big PITA; tl;dr when porting this into qemu
things that seem like they should work don't in Rackspace, and without
being able to see the operator side of the cloud to understand what
it's actually doing it's just an exercise in frustration).
Similar to the openafs situation, the code is available from the PPA
but the history has been kept in personal repos and uploaded manually.
Having it go through gerrit is good for transparency and longer term
maintenance.
We'll have to fiddle the upload jobs, etc. so it works for both
openafs and this; so this is just the first step to get things
started.
[1] https://docs.openstack.org/diskimage-builder/latest/developer/vhd_creation.html
Change-Id: I92b9c65ade7fba2851fd798bad4f658da400dec4
We have branches for each distro we wish to build against, and then
the master branch is empty and doesn't need to build anything. So
don't match the master branch for building.
Change-Id: I3dcba52c999d0b6a7648bad81ae7a8472fbe1058
The promote job lives in openstack/openstack-zuul-jobs where the
secret for uploading is. If the promote job is put in by
project-config, it should be able to access the secret.
Just to keep things together, add the gate/check jobs too.
Change-Id: I3307d89acfac8d81b2f7e1d711cb0b2bf7abf676
This is a project to hold things related to building the OpenAFS
packages used by OpenDev infra. These packages are pushed to a PPA
which is consumed by our production machines.
We keep a separate PPA for these packages as we have had occasions in
the past where we either needed more recent versions of OpenAFS for
various platform support, or had to apply patches with some urgency to
keep things going. Being able to quickly produce new packages has
been very helpful.
Previously these have been created by hand, where somebody uploads the
debian package bits to the PPA manually and a .deb is produced. Of
course the source of those packages is available, but it's not very
git-ops-y or collaborative.
This started in I07780595331da29af9f72185cbb3499210e89c19 where
fungi's concerns that I argued against were completely correct.
Trying to build across xenial -> jammy with one debian/* directory is
not going to work, and checking in multiple trees is very unwieldy in
that repo.
This proposes a separate repo where we can keep branches for each
distro's build. We can then use the existing infrastructure we've
built to build the source packages and push to the PPA for building.
I've chosen the name with "infra-" in front to make it clear these
aren't supposed to be general purpose packages in any way, but are for
opendev infra use. I've put this in the openstack tenant because the
build bits are still in openstack/openstack-zuul-jobs for historical
reasons -- this is where we do similar builds for RPM (which uses AFS
publishing jobs, and has openstack embedded in paths, etc.) and it
makes sense to keep them together. We can consider moving everything
under the opendev tenant in the future.
Change-Id: Ie00c42857e7a541aa1ccb8fe480756c1e7a38dc4
Once we are happy with the results of the parent change we can land this
change to boot test nodes on the new arm64 jammy images.
Change-Id: I24a72279b053422677c3d35ce68fb76e89cc98d4
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
supports https.
Change-Id: I455568f1e261060aefe555e9f5b4ef0830b60157
Nothing seems to be building/booting in linaro-us at the moment. Due
to holidays it make take a little time to get this working on the
remote side. Set this to 0 for now to stop trying to use nodes here.
Change-Id: Ie4be6ad9fa261a4ca7c6a0966ddbd66e413002fd
This change is to end the project gating for the
openstack-helm-docs repo as step 3.1 of retiring the repo.
Change-Id: Ic145858311f887be0eb336c6f27be591fbd07175
These repos will be retired as the ELK systems are being shutdown. That
means the puppetry is no longer retired. Even if we were going to
resurrect these systems they would need to be managed with our modern
config management instead.
Change-Id: I24dd487baea84efab910331451463adb8cb6d99f
This charm implements a 3PAR backend for cinder, acting as
a subordinate charm.
Change-Id: I14c6bd857a09cab07546def009c654738b085c46
Required-By: I16075836abd321d53089d123a711c586b7597a5c
Zuul
Dr. Jens Harbott
Ghanshyam Mann
Ian Wienand
Michael Johnson
Clark Boylan
OpenStack Proposal Bot
Balendu Mouli Burla
Gage Hugo
Luciano Lo Giudice