This appears to be a straightforward bug fix release according to the
release notes:
https://github.com/go-gitea/gitea/blob/v1.16.8/CHANGELOG.md
No template change between v1.16.7 and v1.16.8 according to git.
Change-Id: I0b9bb2f15beb7d3b1541c02e6e96601d25449e33
In our onging quest to find a stable upstream source, switch this to
the facebook mirror which seems to have been working well enough for
centos.
While we're here, reduce the frequency a bit as there's no need to
sync every two hours; it's a bit unfriendly to the remote end.
Change-Id: I50f38b58b3f0c0557fb1e2e0667a17a4f1d1dec6
It appears our opensuse mirror upstream has added an extra opensuse/ in
the path to the opensuse packages that we mirror.
Currently we fail with:
rsync: [sender] change_dir "/distribution/leap/15.2/repo" (in opensuse) failed: No such file or directory (2)
Browsing the repo via https we see the content exists at:
https://mirror.clarkson.edu/opensuse/opensuse/distribution/leap/15.2/repo/
which includes an extra opensuse/ path segment. Now it is possible that
https and rsync have different root dirs, but considering the current
error trying this seems reasonable.
Change-Id: I37aa701af409a58d228c22d664ad0f49a23a1fc5
If borg sees an ansible tmp file just before it is removed by ansible
then we can get errors of this form when running borg:
stat: [Errno 2] No such file or directory: '/root/.ansible/tmp/ansible-tmp-$IDENTIFIER'
This causes the backup run to report failure. Address this by adding
/root/.ansible/tmp/* to our borg backup excludes list.
Change-Id: Ie2c7081a4510959f6514b1cb7eb8facc4ac129fb
Apparently upstream stopped updating docker hub images semi recently. We
should pull from the quay.io location instead. As far as I can tell
docker.io/jboss/keycloak and quay.io/keycloak/keycloak orginate from
https://github.com/keycloak/keycloak-containers so this switch is in
theory fine. But I guess we'll find out.
Change-Id: I42c4a62468a5960332126fec90fcf6307c5b6674
Now that we're retiring the third-party-ci-announce mailing list,
which we never really used consistently anyway, just tell
third-party CI operators to make sure the E-mail address on their
account is current and reachable.
Change-Id: I6186149de25b06f2982702143a807de8bb01be73
This is the latest bug fix release. Upgrade to it to pull in those bug
fixes. You can see the full list of changes in the release notes:
https://github.com/go-gitea/gitea/blob/v1.16.7/CHANGELOG.md#1167---2022-05-02
I've checked template diffs between v1.16.6 and v1.16.7 and they are
empty.
Change-Id: I5c8cb5bf02ab5ca8f64da25f1384291921ba8bba
According to the docs [0] this shouldn't be necessary as performance
logging only happens if a performance tracing plugin is installed.
However according to this repo discuss thread [1] there is always a
dummy performanceLogging instance installed. This same thread identifies
this as a likely source for large increase in memory utilization by
Gerrit when upgrading to 3.5.
Let's explicitly disable this tracing due to the memory overhead in prep
for our 3.5 upgrade. We can always flip the setting if we install a
performance tracing plugin in our Gerrit.
[0] https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#tracing
[1] https://groups.google.com/g/repo-discuss/c/QUD7_LsEVks/m/kBDEeam4AgAJ
Change-Id: Iff438695aa6488fb5886120121946494b1edf003
Because we proxy to Gerrit and set listenUrl with a proxy-http:// prefix
httpd.requestLog is disabled by default. We choose to explicitly enable
it here to add more logging to the Gerrit system even if this logging is
slightly less useful when behind a proxy. In particular this logging
will track memory utilization per request which we can use to benchmark
change query memory cost between 3.4 and 3.5.
Change-Id: Ia3ccf820ee0e5ca7d68bcc37da7004dea2ad7128
In preparation for retiring a number of mailing lists from
lists.openstack.org which have had no activity for over three years,
remove their configuration so our deployment automation won't
recreate them once they're gone. Also remove references to the
third-part-announce list in our documentation, since that's one of
the unused lists we're removing. See the announcement at
http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027404.html
for details.
Change-Id: Ieedd8613363039d19d3ae47f1a83a38747419bdc
The status.openstack.org server is offline now that it no longer
hosts any working services. Remove all configuration for it in
preparation for retiring related Git repositories.
Also roll some related cleanup into this for the already retired
puppet-kibana module.
Change-Id: I3cfcc129983e3641dfbe55d5ecc208c554e97de4
The openstack health server was removed but cleaning up its groups was
missed. Fix this by removing the group from our ansible configs.
Change-Id: I84fdf290e359609fc0854719fa9ecb032c7ea254
I think this was overlooked in the removal of the ELK stack with
I5f7f73affe7b97c74680d182e68eb4bfebbe23e1, the repo is now retired.
Change-Id: I87bfe7be61f20a7c05c500af4e82b787d9c37a8c
As an overall clean-up effort to free space on our mirror volumes,
stop mirroring source packages for the debian package repository.
According to codesearch, the configure-mirrors role in
zuul/zuul-jobs adds deb-src lines for it, so we need to wait on
merging this until a change merges to switch its default behavior or
we override the default behavior in opendev/base-jobs. It also won't
take effect immediately, and will require a manual step to prune the
old packages from the filesystem once this configuration update has
deployed.
Change-Id: Ia5777770e178385b7326c97728c875f302c1e1f0
Depends-On: https://review.opendev.org/839593
As an overall clean-up effort to free space on our mirror volumes,
stop mirroring source packages for the ubuntu package repository.
According to codesearch, no jobs in our system add deb-src lines for
it so this should be entirely safe. It also won't take effect
immediately, and will require a manual step to prune the old
packages from the filesystem once this configuration update has
deployed.
Change-Id: Ie2aa6bdf43721c9ceacea54f7f5bc928883287a7
As an overall clean-up effort to free space on our mirror volumes,
stop mirroring source packages for the various debian-docker-*
repositories. Note that this should be a no-op as those repositories
don't appear to provide source packages anyway.
Change-Id: I51c723782c7aa08dc29c839b8e46c2dd6d8c8d41
This adds package mirroring for Jammy Docker packages. One of the (I'm
sure) many steps to spin up Jammy in our CI environment.
Change-Id: I2c3fe6fed07ac36aa65b6f060012705ff940f69a
Our CI jobs generally don't make use of source packages, and because
pulling them requires a separate line in sources.list anyway any
jobs which want them can add an official mirror source easily.
Remove from the configured architectures list in ubuntu-ports
initially, since ARM jobs are even less likely to be impacted by
this due to their scant number and limited frequency. This will
allow us to evaluate the fallout and determine whether manual
cleanup is needed afterward.
Change-Id: Ib647b6733529d965fa9caa92ad4d123639510083
We're trying to start mirroring Ubuntu 22.04 LTS packages, and their
indices are now signed with the 2018 Archive Signing Key which we
haven't yet imported. Add it.
Change-Id: I88cabf8a703ef0086e58b8f6cd65bf54321f7998
We have managed to prune our service list quite a bit and in the process
have orphaned some group var data for those services. Remove the group
vars for:
ask
graphite_opendev.org
groups
openstackid(-dev)
pbx/asterisk
Change-Id: I099624e5958d17349cd3d197d9d9cb4da87a5b38
Clark Boylan
Zuul
Ian Wienand
Jeremy Stanley
Dr. Jens Harbott