This jobs are super stale now (py35?) and don't seem to function
reliably. Rather than update the config here in project config we remove
the jobs here with the intention of adding new jobs that make sens
in the in repo config.
Change-Id: I35704d26099b6f3fd5a03adc22670c023be4a4b0
Add a project for defining the zuul jobs for testing charms.
Change-Id: I69a9c9f388371a7a8ad1c7fe5cfc8f6c444d4f45
Required-By: I07ace283a8255f106c141d7bea06618f802e3b51
Since the PTI switched the supported python versions for the current
cycle from 3.8+3.9 to 3.9+3.10, we want to update the constraints
generation accordingly. Since we don't have a stable platform where we
can run both py3.9 and py3.10 in parallel, generate constraints only for
py3.10 for now.
Change-Id: I4a4d9cb6e292bb693ae424be0928501fed81113f
Zuul is looking at dropping ansible 5 support. By updating our default
ansible version to 6 early we can provide valuable feedback to the Zuul
project. That said we expect this to function. The Zuul Zuul tenant is
already running under ansible 6, and I've done some testing with
devstack [0] that appears to show those jobs running happily.
The openstack release is now out the door which makes this a good time
to change the zuul default.
[0] https://review.opendev.org/c/openstack/devstack/+/858436
Change-Id: I61493e74d9955a444326d72e085f511a838f88dd
Our various nodepool launcher configs have gotten out of sync with
recent additions. Try to match them up better by adding rockylinux
and openeuler to places where they were missing. In particular, this
addresses an inconsistency on nl04 which caused the service to crash
at last restart due to rockylinux missing from the main diskimages
list.
Change-Id: Ie157ab7f667dbdc313b7fdbfc1df71874e8bd0fc
This seems to have been overlooked when the label was added to other
launchers, and is contributing to NODE_FAILURE results for some
jobs, particularly now that fedora-latest is relying on it.
Change-Id: Ifc0e5452ac0cf275463f6f1cfbe0d7fe350e3323
Zuul now expects queue to be a project attribute, and won't process
pipeline definitions which still include it. Fix immediately.
Change-Id: Id2968b1b4ed8996365cc4cd4fe1e30f1e7ea64f9
Zuul will eat its own dogfood to ensure that new functionality like
Ansible 6 support works properly.
Change-Id: I577b1af5bca4fc44cd03e9d5f95306b3cd7f8b08
Add new charm that enables Keystone to support OpenID Connect via
Federation.
Change-Id: Ic758858db00a72a136e21c18f452df07f4ea74c2
Required-By: I1b7495f0a5010f9768845882a6e072b5be3f18b9
From 2023.1 cycle, TC agree to make python version
template to be unversioned
- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/856903
This commit updates the release script to update the
unversioned template from next cycle.
Change-Id: Icf03e279bf574f5ff0c0f14b53c4ef76b6098c46
It's https://github.com/ansible/ansible-lint/issues/2320 which is
blocking our use of newer ansible-lint (though it's worth revisiting
whether testing with ansible-lint is still of any real value).
Change-Id: Ie3e42df7f90e5349bf1513e8896b1d5e16125b42
The STS-Silicom app is intended to be used to configure
PTP/SyncE configurations on certain NICs from the Silicom
vendor.
Story: 2010213
Task: 46215
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: Ie6bf611af6f6e61aefd54dbfeed61896c98b437b
The zuul pipeline reporter for merge-failure is now canonically called
merge-conflict. The old name has been deprecated and will be removed in
the near future. Update our config to use the new name.
Change-Id: Iaf49c8231618c7a24a0dca7f23d5b3770818dc80
The element was missing from the configuration due to an oversight, this
change brings it in line with C9S as well as Rocky 8 to have EPEL
enabled.
Change-Id: I080f8118ccf411e363e0f7c2433dfaa9e911dd15
We try to test our job content with the same ansible-lint versions
used by the zuul/zuul-jobs repository. Adjust our exclusions to
match what it's using, for consistency and ease of future
maintenance.
Change-Id: I2300e8950780245a38f68ce9cc5aa5ff62e65e40
For local runs of testenv:linters we cache all the external Ansible
playbooks and roles ansible-lint will need to reference in order to
validate content in this repository. We build that cache in a .cache
directory, but not everything in the cached repositories is suitable
for flake8 checking, so add that directory to its exclusion list.
Also add the same directory to .gitignore, so Git will stop
complaining about it being untracked.
Change-Id: I1f740edd75cc7f6ba0f4a73f0a409a620b437b16
Currently the value persists only if it's the max or min, and only
when there are no code changes or if it's a trivial rebase.
The behavior we'd like is that the assigned priority should persist
across the series of patch sets, even if there are code changes,
because this label indicates the relative importance of getting eyes
on the review, and is not directly involved in the code being approved.
A -1 Review-Priority ("Branch Freeze"), in addition to being sticky,
will continue to block submission of the patch.
Change-Id: Iee323ab80f9a58bf49827c23934560edfad57bf3
ansible-lint introduced a regression as described in
"Don't use ansible-lint 6.5.0" I1770e034772b55b993d276d580c5a75d059bd822
the fix is still in draft and 6.5.1 has been released so lets skip that
too
Change-Id: I641a1246f870869153df782381fd9dafa180da26
We have some skips in our playbooks which 6.5.0 ignores because of
https://github.com/ansible/ansible-lint/issues/2320 so block that
version and hope the fix makes it into the next release.
Change-Id: I1770e034772b55b993d276d580c5a75d059bd822
Generating these updates on a daily basis isn't realistic and they often
take several modifications to merge. The current process withing the
requirements team is to modify the topic and then work on them. The
next time the periodic pipeline triggers we "ignore" the new change.
This change switches to the periodic-weekly pipeline to better match the
available workflow of the requirements team
Change-Id: I478a64b21d9f19ece21ec5fb7a1327a106664529
Update the sshd_config on our test nodes to accomodate what appears to
be an increase in ssh scanner traffic. In particular LoginGraceTime
defaults to 120 seconds. We reduce that to 30 seconds to cycle
connections more quickly. Then we also increase the maximum number of
connection startups to 30 from the default of 10. We also reduce the
random fail rate from 30% to 10% between 31 and 100 connections.
I'm not entirely certain this will fix things, but based on what we've
seen from logs it may be what we need to make ssh to test nodes more
reliable.
Change-Id: Ifacf7d00de157ab2fb60cde990f0b49f03f71415
This updates ansible-lint to the 6.x releases. It also updates the
ansible installed to our current zuul version.
It cleans up the config file and marks it as yaml. A few new
exceptions are added with explainations.
We don't need to fake the zuul_return by telling ansible-lint to mock
it. This is added to the config, and we can remove the stub file.
A constant source of problems running this locally is that you have to
have the other role repos checked out so ansible-lint can do its
checks. Add a smaller helper script for doing this locally. In the
gate, ANSIBLE_ROLES_PATH is set to the Zuul checkouts of these
projects. Locally, add a smaller helper "ansible-lint-roles-cache.sh"
that pulls the projects into a .cache directory. If they are already
there, they get updated. By default locally we will use these
checkouts. This way, "tox -e linters" just works without having to do
anything else.
This also modifies the xargs to run the check all at once, instead of
fork for each file. I did try autodetection but it seems like other
yaml files in the roles/playbook directories still confuse
ansible-lint.
Also I don't think we need a ansible-playbook --syntax-check step;
ansible-lint covers that.
Change-Id: I972f73037b9f904a555b81f3835ca5261639ed01
