- Zuul-discuss - lists.opendev.org

Re: Zuul 4.11.0 released
by James E. Blair 16 Dec '21

16 Dec '21

On 12/16/21 1:12 PM, James E. Blair wrote: > The Zuul team is pleased to announce the release of Zuul 4.11.0. > > Download it from PyPI: https://pypi.org/project/zuul > > Find container images at: https://hub.docker.com/u/zuul > > The release notes, included below, are also available in the > documentation with hyperlink references: > > https://zuul-ci.org/docs/zuul/4.11.0/reference/releasenotes.html > > New Features > ============ > > * The new variable zuul.playbook_context as well as new variables under > zuul.projects have been added to help debug or audit the playbooks and > roles used by Ansible when running jobs. > > * These variables describe the repo configuration used for the playbooks > and roles of each Ansible execution. These repos may have a different > state than the workspace repos. > > * It is now possible to disable connection pooling in the Gitlab driver > with <gitlab connection>.disable_connection_pool. This option may be > useful under adverse network conditions. > > * The optional prometheus service now also includes endpoints for > readiness and liveness checks. See Liveness Probes for details. > > * Allow an authorized user to dequeue changes from the Web UI's status > page. > > * Add authentication in the web UI. Zuul's web UI can be configured to > authenticate users against an Identity Provider supporting the OpenID > Connect protocol. > > Upgrade Notes > ============= > > * Users upgrading from previous versions of zuul will need to run zuul > delete-state to delete Zuul's ephemeral state from Zookeeper. The > ephemeral state produced by older versions of zuul is not compatible > with this release. This command should be run while all Zuul services > are stopped to prevent writes to the Zookeeper database. More > information on this command can be found in the documentation: > https://zuul-ci.org/docs/zuul/reference/client.html#delete-state > > * The prometheus endpoint would previously serve metrics at any URI. It > now only returns metrics on the / and /metrics URI. The latter is > recommended. > I encourage folks to consider this a release candidate for Zuul v5. At this point the multi-scheduler functionality is complete but has seen limited production use. Please try it out and look for problems. If you do find problems, run "zuul delete-state" and roll back to 4.10.4. Additionally, between now and the v5 release, we will be removing the long-deprecated gearman RPC system, which means that if you use "zuul enqueue" and similar commands, you should switch to using zuul-client with a self-generated authentication token. This and all recent version 4.x releases support both, which makes this an excellent time to switch. -Jim

2 1

[Diversity] D&I WG Meeting Time and IRC vs Video Poll
by Amy Marrich 14 Dec '21

14 Dec '21

Hi everyone, The Diversity and Inclusion WG is holding a poll to see if there would be interest in attending if it were on another day and time as well as if IRC vs Video would be preferred. We currently meet the first Monday of the month at 17:00 UTC. And hope to have a planning meeting as our first meeting of the year. Our first meeting of the new year is slated for January 3rd at 17:00 UTC and for IRC. We will take the poll results into consideration and may cancel the January meeting to allow folks to plan on attending in which case February's meeting would be the first of the year. Please vote for your preferred days and times AND also for IRC and/or Video. https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link We are keeping to morning hours to encourage participation from EMEA but not overly early for PST folks to attend. We will keep the poll up through the end of the year. Please feel free to reach out with any questions or concerns and remember the Diversity and Inclusion WG is for ALL projects under the Open Infra Foundation! Thanks, Amy (spotz)

1 1

Additional zuul comments apart from warnings
by Muhia Nyambura 13 Dec '21

13 Dec '21

Hello all, Is it possible to return other "Generic" comments apart from Warnings and File Comments <https://zuul-ci.org/docs/zuul/reference/jobs.html?highlight=zuul_success#le…> ? We would like to return some additional information (URLs) together with the Build URL in our Gerrit comments without having to go to the Zuul instance to access these links - like how we have it for artifact URLs <https://zuul-ci.org/docs/zuul/reference/jobs.html?highlight=zuul_success#re…> . Do you have suggestions on how I can achieve this? Or is this something that you could possibly look into adding? BR, Nyambura.

1 0

zuul admin GUI - what now?
by Matthieu Huin 24 Nov '21

24 Nov '21

(Bringing this to the ML as the BOAF session ran out of time) Hey folks, I'd like some guidance and opinions on how to go forward with the Zuul Admin GUI changes [0]. My main concern is how to ensure reviews can be done in the easiest way for everyone. I took some steps in that direction: * I have provided a test docker compose based on the demo compose in the documentation [1]. This compose lives on top of the patch chain, so all the changes can be tested at once. It is also possible to cherry-pick the change on top of any specific patch you'd like to test in particular. It is not perfect, but it does set up authentication via OpenID Connect for zuul and gerrit, allowing to experiment further with the new features. Is there anything I should do to improve this ? Or should I leave this as is, as it is not intended to get merged (it's meant for demo purposes only) ? * I have reorganized the patch chain so that the python and the JS changes are strictly separated. Furthermore, the changes to the python components are at the beginning of the patch chain. I think it'd be great to get these reviewed and merged ASAP (they're not big changes), because one big downside of the compose mentioned above is that it requires rebuilding the zuul containers locally before it can run. Once these changes are integrated, the compose can run on the latest published containers. * I've added various screenshots and video captures to the reviews, so that reviewers can get an idea of what the changes would look like without having to deploy. * I am currently working on deploying a public test instance based on the demo compose. Is there anything else I can do to get this moving forward ? Cheers, MHU [0] https://review.opendev.org/q/topic:%22GUI_admin%22+(status:open%20OR%20stat… [1] https://review.opendev.org/c/zuul/zuul/+/769943 -- Matthieu Huin Senior Software Developer Red Hat <https://www.redhat.com> <https://red.ht/sig>

3 7

install and use ansible collections in zuul v3 ansible native job?
by Marios Andreou 23 Nov '21

23 Nov '21

hi folks long story short: can we install and use ansible collections in a zuul v3/ansible native job? In the tripleo-ci squad we are trying to use the tripleo_overcloud_image_build role from the tripleo-operator-ansible collection [1]. We are already using other roles from this collection - e.g. there [2]. This is possible because in that case we have zuul calling bash calling ansible... which means we get to configure collections in the bash bit setting ANSIBLE_COLLECTIONS_PATHS [3] before invoking ansible. For the case I'm having trouble with - what i refer to as ansible native - here https://review.opendev.org/#/c/733818/33/roles/oooci-build-images/tasks/mai… we have a zuul job playbook directly trying to install and use a collection. Currently it fails because instead of collections: (doesn't work " 'collections' is not a valid attribute? [4] ) I am trying to use include_role but then it can't find the collection's modules "ERROR! no action detected in task" [5]. I tried to set it in ansible.cfg but that won't work and anyway it is surely the wrong approach. The one thing left to try is to explicitly require ansible 2.9 for the job - but wanted to reach out and see if anyone else has any problems trying to install and use ansible collections (with modules importantly) as part of a zuul v3/ansible native job. thanks for reading and for any comments, marios [1] https://github.com/openstack/tripleo-operator-ansible/tree/master/roles/tri… [2] https://opendev.org/openstack/tripleo-quickstart-extras/src/commit/55e74bb8… [3] https://opendev.org/openstack/tripleo-quickstart/src/commit/299131bcc6dca86… [4] https://23fd78c0f6b01b9c4209-59c294b8f46eb75cda2bd004e2a1c97f.ssl.cf1.rackc… [5] https://2063b7e2bb67f86f8ec5-87fe67c942382c6ee875c514bffa4f21.ssl.cf2.rackc…

3 8

dynamic job list
by Åsmund Østvold 18 Nov '21

18 Nov '21

Hi All, We are looking into optimizing what jobs need to run. After building we know what artifacts that did change. Knowing this we know what tests that need to be executed. Is there a way to feed that back to the zuul buildset? A change only changes artifacts used by testx and testy compared to what has already been tested. So the static project: project: check: jobs: - build Is at runtime converted into: pipeline- project: check: jobs: - build - testx - testz Cheers, Åsmund

2 1

Indexing Zuul build logs
by Tristan Cacqueray 05 Nov '21

05 Nov '21

Hi, I would like to discuss the best practices for build logs processing. The goal is to improve the user experience when debugging a job that produces a lot of logs (e.g. >10MB) and to help discover failures that are transients and unrelated to a particular build. The existing options are (please reply with your own solutions): - opendev/puppet-log_processor : a gearman service that can be notified through a post job task to trigger build log indexing in logstash. This also provides a classify-log.crm function to annotate log with a score. - openstack/ci-log-processing : a work in progress service to replace the post job task and use the log_processor through the builds api. - opendev/log-classify : an import of my logreduce tool that runs as a post task to provide an html report directly along the build log. https://softwarefactory-project.io/cgit/logreduce/tree/README.rst (The initial opendev reviewes are still in open). - github.com/bmwcarit/zubbi : a service to index jobs and roles in elasticsearch. This is not exactly related to the goal, but it is worth mentioning it. I am wondering if Zuul shouldn't support elasticsearch directly, by providing a `upload-logstash` role in zuul-jobs, and by supporting browsing the elasticsearch api directly from zuul-web. This would remove the need for an extra service to do the indexing, and we wouldn't have to process and store the logs twice. Am I missing something, how do you process build logs? Regards, -Tristan

3 4

[Diversity] Diversity and Inclusion Meeting Reminder
by Amy Marrich 31 Oct '21

31 Oct '21

The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Monday November 1st, at 17:00 UTC in the #openinfra- diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (apotz)

1 0

Zuul virtual meetup
by James E. Blair 19 Oct '21

19 Oct '21

Hi, Some folks registered an interest in the Matrix channel to have a virtual meetup to discuss their experiences with the zuul-operator. It's PTG week, but most of the PTG slots convenient for the participants are already booked. So we'll just schedule an ad-hoc meetup for this Thursday, 2021-10-21, at 14:00 UTC. It won't appear on the official PTG schedule. Join at this URL: https://meetpad.opendev.org/zuul-2021-10-21 We'll start by discussing the Zuul operator, but general Zuul discussion is welcome too. Expect something like a birds-of-a-feather session. Hope to see/hear/chat with you there. -Jim

2 1

[Diversity] [PTG] Diversity nd Inclusion Session at PTG
by Amy Marrich 15 Oct '21

15 Oct '21

Hi Everyone, The Diversity and Inclusion WG will be meeting during the PTG on Monday October 18th at 14:00 UTC in the Diablo room. We welcome all Open Infrastructure project to attend and we would be happy to assist you with any questions you might have in regards to the Inclusive Naming initiative that OIF began last year, We plan to do a review of the current CoC or going through the current code base for the projects to find instances where changes are needed to provide both examples and patches where appropriate to assist in these endeavours. The activities we focus on will be determined by attendance during the session, Thanks, Amy (spotz) on behalf of the Diversity and Inclusion WG

1 0

Learn how users are using Zuul at OpenInfra Live: Keynotes
by Jimmy McArthur 12 Oct '21

12 Oct '21

Hi everyone! You might have heard that the OpenInfra Foundation is hosting its largest free virtual event of this year—OpenInfra Live: Keynotes OpenInfra Live: Keynotes [1] Date and time: November 17-18 (1500-1700 UTC on each day) Register for free [2] This two day special episode is your best opportunity to meet the newest players to the OpenInfra space and hear about how open source projects, such as Zuul, are supporting OpenInfra use cases like hybrid cloud. You will also have the chance to deep dive into the Zuul user survey results since the launch of the Zuul User Survey in March 2020. Here is a preview of the Zuul user survey results findings: Zuul has an incredible 69% of User Survey environments running in production, spanning industries including automotive, retail and public cloud providers. Gating, speculative merge and cross-project dependencies continue to be features praised by users. The full report of the Zuul user survey will be distributed during the OpenInfra Live: Keynotes, so make sure you are registered for the event [2]. Can’t make it to the event? Register anyway, and we will email you the recording after the event! At OpenInfra Live Keynotes, you will also have the opportunity to interact with leaders of open source projects like OpenStack and Kubernetes to hear how the projects are supporting OpenInfra use cases like hybrid cloud gain insight into public cloud economics and the role open source technologies play celebrate as we announce this year’s Superuser Awards winner. This will be the one time everyone will be coming together this year. Come interact with the global OpenInfra community—Live! [1]: https://openinfra.dev/live/keynotes [2]: https://www.eventbrite.com/e/openinfra-live-keynotes-tickets-169507530587 Cheers, Jimmy

1 0

Diversity and Inclusion Meeting Reminder - Tooday
by Amy Marrich 04 Oct '21

04 Oct '21

The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Monday October 4th, at 17:00 UTC in the #openinfra- diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (apotz)

1 0

Use of "zuul delete-state"
by James E. Blair 27 Sep '21

27 Sep '21

Hi, For those who are tracking master: we ran into some issues recently that required changes to how we store objects in ZooKeeper. If you have run recent commits of Zuul from master and upgrade, you may run into issues starting Zuul because of the change in data format (it may manifest as a crash on startup with a KeyError or something similar). If you do so, run this command to delete the ephemeral data from ZooKeeper: zuul delete-state That will delete all the cached data, job requests, etc, but leave Nodepool and secret key storage intact. It may take a few minutes to run, and the next time you start your scheduler it may take a little longer. Friendly reminder that if you encounter any ZooKeeper-related errors, this command is always there as an escape hatch. -Jim

1 0

"Merge failed" in promote pipeline
by Christian von Schultz 20 Sep '21

20 Sep '21

Hello everyone, I'm trying to make a promote pipeline, using the supercedent pipeline manager. I added a simple job just to see that it works, and it doesn't. The message in Gerrit is "Merge Failed", which I didn't expect from a post-merge pipeline. I thought it would just check out the commit in question and run the job. Do I need to tell it to do that? My pipeline configuration for the promote pipeline is based on this: https://zuul-ci.org/docs/zuul/reference/drivers/gerrit.html#reference-pipel… The project is running with "merge-mode: cherry-pick", but for changes that are already merged, I didn't expect any extra cherry-picking. How is this supposed to work? I'm running Zuul 4.3.0. Scheduler log says: > 2021-09-20 12:44:19,779 DEBUG zuul.Pipeline.embedl-tenant.promote: [e: 6d632d0932ab48189dc4f91098670f68] <QueueItem 98818e7cef9f43ca8aa492387d772bd7 for <Change 0x7fdf74331a90 embedl 1174,2> in promote> is a failing item because ['it has a merge conflict'] Executor log says: > 2021-09-20 12:44:17,771 DEBUG zuul.Merger: [e: 6d632d0932ab48189dc4f91098670f68] Unable to merge {'project': 'embedl', 'connection': 'gerrit', 'merge_mode': 3, 'ref': 'refs/changes/74/1174/2', 'branch': 'work/promotebranch', 'buildset_uuid': 'e2ccdf93250047578dba0ea8adf7b82f', 'number': '1174', 'patchset': '2', 'oldrev': None, 'newrev': None} > Traceback (most recent call last): > File "/usr/local/lib/python3.8/site-packages/zuul/merger/merger.py", line 1000, in _mergeChange > commit = repo.cherryPick(item['ref'], > File "/usr/local/lib/python3.8/site-packages/zuul/merger/merger.py", line 541, in cherryPick > repo.git.cherry_pick("FETCH_HEAD") > File "/usr/local/lib/python3.8/site-packages/git/cmd.py", line 588, in <lambda> > return lambda *args, **kwargs: self._call_process(name, *args, **kwargs) > File "/usr/local/lib/python3.8/site-packages/git/cmd.py", line 1134, in _call_process > return self.execute(call, **exec_kwargs) > File "/usr/local/lib/python3.8/site-packages/git/cmd.py", line 931, in execute > raise GitCommandError(redacted_command, status, stderr_value, stdout_value) > git.exc.GitCommandError: Cmd('git') failed due to: exit code(1) > cmdline: git cherry-pick FETCH_HEAD > stdout: 'Not currently on any branch. > You are currently cherry-picking commit fe48d19. > > nothing to commit, working tree clean' > stderr: 'The previous cherry-pick is now empty, possibly due to conflict resolution. > If you wish to commit it anyway, use: > > git commit --allow-empty > > Otherwise, please use 'git reset'' Best regards, Christian von Schultz

2 1

zuul-jobs testing at an impasse
by Jeremy Stanley 17 Sep '21

17 Sep '21

A quick summary... This week, a new protobuf release dropped Python 2.7 and 3.5 support, causing tox-py27 builds for zuul-jobs changes to fail, raising SyntaxError importing roles.upload-logs-base.library.test_zuul_google_storage_upload. The proposed fix is to use an environment marker to pin to earlier protobuf on Python<3.6 for now: https://review.opendev.org/809460 Another slightly more tricky problem is that this week, a new Virtualenv release bundled a new major version of SetupTools which dropped support for its old use_2to3 option. This has caused problems for a number of very old Python packages, but in our case specifically funcparserlib which was last fully released in 2013. Using latest virtualenv, attempts to install funcparserlib or anything which requires it will just break. We have one document in zuul-jobs (docker-image.rst) which uses blockdiag and seqdiag directives, and that is indirectly responsible for pulling in the funcparserlib package. Thankfully, the funcparserlib maintainers acted quickly and proposed an alpha release which we can explicitly require until the blockdiag project merges a pending pull request to do so itself, and this is proposed already: https://review.opendev.org/809885 Unfortunately, that new alpha release also drops Python 3.5 support, meaning we can't build the zuul-jobs docs (well, docker-image.rst specifically) on Ubuntu Xenial. That might seem like a small thing, we build and publish the zuul-job docs with much newer Python anyway, however the way we've chosen to test the fetch-sphinx-tarball role is to run `tox -e docs` for zuul-jobs on lots of different platforms, one of which is Ubuntu Xenial. Dropping support for Python 3.5 is happening in new releases of projects right and left, and as of January 2022 pip itself intends to make a new release which will no longer work on Python 3.5, so if we intend to continue testing things on Ubuntu Xenial at all, we're almost certainly going to need to work out how to do so with older toolchains which can still work on its Python version. So here's the dilemma, and my question to you. Do we: A. rework the fetch-sphinx-tarball role test to no longer use the docs/requirements.txt in zuul-jobs? B. redo docker-image.rst to switch from blockdiag and seqdiag to something else (another Sphinx plugin, pre-rendered images...)? C. adjust tools/update-test-platforms.py to allow us to exclude specific autogenerated jobs we know can never work and use that to drop the zuul-jobs-test-fetch-sphinx-tarball-ubuntu-xenial? D. remove Ubuntu Xenial testing for zuul-jobs in general? E. some other solution I'm too braindead to come up with on a hot Friday afternoon? Feedback on where I should go from here would be much appreciated! -- Jeremy Stanley

1 1

Mailing lists offline 2021-09-12 for server upgrade
by Jeremy Stanley 12 Sep '21

12 Sep '21

On Sunday, September 12, the OpenDev sysadmins will be performing operating system upgrades for the server hosting the lists.airshipit.org, lists.opendev.org, lists.openstack.org, lists.starlingx.io, and lists.zuul-ci.org sites. Expect extended outages for message delivery and access to archives between 15:00 UTC and 21:00 UTC, though messages sent to the mailing lists at these sites should queue normally and be delivered automatically after maintenance activities have concluded. If you have any questions, feel free to reply to this message, or find us in the #opendev channel on the OFTC IRC network. -- Jeremy Stanley

1 1

Debugging zuul-registry failures when using buildkit
by Ian Wienand 01 Sep '21

01 Sep '21

Change https://review.opendev.org/c/opendev/system-config/+/805933 is using DOCKER_BUILDKIT=1 to build an image (gitea) but has a requirement to pull another image (the new "assets" image, proposed with it's parent https://review.opendev.org/c/opendev/system-config/+/805933/) from the intermediate registry. This reliably fails as you can see from any of the zuul results. The failure is --- root@ubuntu-focal-ovh-bhs1-0026222696:/home/zuul/src/opendev.org/opendev/system-config/docker/gitea# DOCKER_BUILDKIT=1 docker build . ... => ERROR [internal] load metadata for docker.io/opendevorg/assets:latest ------ > [internal] load metadata for docker.io/opendevorg/assets:latest: ------ failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = failed commit on ref "config-sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07": unexpected commit digest sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, expected sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07: failed precondition --- I enabled debugging on the docker daemon and it produces the following --- Sep 01 03:56:36 ubuntu-focal-ovh-bhs1-0026222696 dockerd[5392]: time="2021-09-01T03:56:36.097177192Z" level=debug msg=resolving host=registry-1.docker.io Sep 01 03:56:36 ubuntu-focal-ovh-bhs1-0026222696 dockerd[5392]: time="2021-09-01T03:56:36.097232892Z" level=debug msg="do request" host=registry-1.docker.io request.header.accept="application/vnd.docker.distribution.manifest.v2+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.image.manifest.v1+json, application/vnd.oci.image.index.v1+json, */*" request.header.user-agent=containerd/1.4.0+unknown request.method=HEAD url="https://registry-1.docker.io/v2/library/golang/manifests/1.16-buster" Sep 01 03:56:36 ubuntu-focal-ovh-bhs1-0026222696 dockerd[5392]: time="2021-09-01T03:56:36.100016964Z" level=debug msg="fetch response received" host="zuul-jobs.buildset-registry:5000" response.header.content-length=921 response.header.content-type=application/vnd.docker.distribution.manifest.v2+json response.header.date="Wed, 01 Sep 2021 03:56:36 GMT" response.header.docker-content-digest="sha256:3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4" response.header.server=CherryPy/18.6.0 response.status="200 OK" url="https://zuul-jobs.buildset-registry:5000/v2/opendevorg/assets/manifests/lat…" Sep 01 03:56:36 ubuntu-focal-ovh-bhs1-0026222696 dockerd[5392]: time="2021-09-01T03:56:36.100201992Z" level=debug msg=resolved desc.digest="sha256:3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4" host="zuul-jobs.buildset-registry:5000" Sep 01 03:56:36 ubuntu-focal-ovh-bhs1-0026222696 dockerd[5392]: time="2021-09-01T03:56:36.100454497Z" level=debug msg=fetch digest="sha256:3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4" mediatype=application/vnd.docker.distribution.manifest.v2+json size=921 Sep 01 03:56:36 ubuntu-focal-ovh-bhs1-0026222696 dockerd[5392]: time="2021-09-01T03:56:36.101860659Z" level=debug msg=fetch digest="sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07" mediatype=application/vnd.docker.container.image.v1+json size=0 --- We see digest="sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07" has size=0; clarkb helpfully noted that the "unexpected commit digest" e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 is actually the sha256 of an empty string. This seems related. The buildset registry output for this is --- 2021-09-01 04:10:11,794 DEBUG registry.authz: Auth ok read 2021-09-01 04:10:11,794 INFO registry.api: HEAD manifest _local docker/dockerfile 1.3 2021-09-01 04:10:11,794 ERROR registry.api: Manifest docker/dockerfile 1.3 not found 2021-09-01 04:10:11,794 INFO cherrypy.access.140461361540832: ::ffff:172.17.0.1 - - [01/Sep/2021:04:10:11] "HEAD /v2/docker/dockerfile/manifests/1.3?ns=docker.io HTTP/1.1" 404 735 "" "containerd/1.4.0+unknown" 2021-09-01 04:10:12,115 DEBUG registry.authz: Auth ok read 2021-09-01 04:10:12,115 INFO registry.api: HEAD manifest _local library/debian buster-slim 2021-09-01 04:10:12,115 ERROR registry.api: Manifest library/debian buster-slim not found 2021-09-01 04:10:12,116 INFO cherrypy.access.140461361540832: ::ffff:172.17.0.1 - - [01/Sep/2021:04:10:12] "HEAD /v2/library/debian/manifests/buster-slim?ns=docker.io HTTP/1.1" 404 735 "" "containerd/1.4.0+unknown" 2021-09-01 04:10:12,119 DEBUG registry.authz: Auth ok read 2021-09-01 04:10:12,119 INFO registry.api: HEAD manifest _local library/golang 1.16-buster 2021-09-01 04:10:12,120 ERROR registry.api: Manifest library/golang 1.16-buster not found 2021-09-01 04:10:12,120 INFO cherrypy.access.140461361540832: ::ffff:172.17.0.1 - - [01/Sep/2021:04:10:12] "HEAD /v2/library/golang/manifests/1.16-buster?ns=docker.io HTTP/1.1" 404 735 "" "containerd/1.4.0+unknown" 2021-09-01 04:10:12,125 DEBUG registry.authz: Auth ok read 2021-09-01 04:10:12,125 INFO registry.api: HEAD manifest _local opendevorg/assets latest 2021-09-01 04:10:12,126 DEBUG registry.api: Manifest opendevorg/assets latest digest found sha256:3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4 2021-09-01 04:10:12,126 DEBUG registry.api: Retrieved sha256 3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4 2021-09-01 04:10:12,126 INFO cherrypy.access.140461361540832: ::ffff:172.17.0.1 - - [01/Sep/2021:04:10:12] "HEAD /v2/opendevorg/assets/manifests/latest?ns=docker.io HTTP/1.1" 200 - "" "containerd/1.4.0+unknown" 2021-09-01 04:10:12,128 DEBUG registry.authz: Auth ok read 2021-09-01 04:10:12,129 INFO registry.api: GET manifest _local opendevorg/assets latest 2021-09-01 04:10:12,129 DEBUG registry.api: Manifest opendevorg/assets latest digest found sha256:3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4 2021-09-01 04:10:12,129 DEBUG registry.api: Retrieved sha256 3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4 2021-09-01 04:10:12,129 INFO cherrypy.access.140461361540832: ::ffff:172.17.0.1 - - [01/Sep/2021:04:10:12] "GET /v2/opendevorg/assets/manifests/latest?ns=docker.io HTTP/1.1" 200 921 "" "containerd/1.4.0+unknown" --- There is a file on the host --- # cat buildkit/content/blobs/sha256/3ae38c942ced144dcbacf8e9895bb553f84de6c8abdfced27c7075f18583f2a4 { "schemaVersion": 2, "mediaType": "application/vnd.docker.distribution.manifest.v2+json", "config": { "mediaType": "application/vnd.docker.container.image.v1+json", "digest": "sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07" }, "layers": [ { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 3122, "digest": "sha256:d400fcf962679c5efdb77b55b187b8afffb53f7342895f0b6f6206cf1fbbac6d" }, { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 1899, "digest": "sha256:1cdb62f96c3d6766a459909f1306f97d174fd4b5fa11a46ecc2f20d8c529db93" }, { "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip", "size": 7671, "digest": "sha256:f7721f02fe31867cdcab1396b7fc132f427ab98fe1f083611b2cc01e3f4fb4a8" } ] --- I note that the "config" here doesn't have a size -- it seems to me from https://docs.docker.com/registry/spec/manifest-v2-2/ it should. So I poked at the original opendev-buildset-registry job that the "assets" image as uploaded to https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… That shows this has a size "2329" --- 2021-08-31 20:36:33,782 INFO registry.api: Get blob _local opendevorg/assets sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07 2021-08-31 20:36:33,782 INFO cherrypy.access.140479630381648: ::ffff:172.17.0.1 - - [31/Aug/2021:20:36:33] "GET /v2/opendevorg/assets/blobs/sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07 HTTP/1.1" 200 2329 "" "containers/5.10.2 (github.com/containers/image)" --- So, I hand edited in this size to the "config" above; to be clear it now looked like ... "config": { "mediaType": "application/vnd.docker.container.image.v1+json", "size": 2329, "digest": "sha256:c250addbd759142b5feb692703a422348faecf3ddfa2cc8191ab43d265c7bc07" }, ... and ... the build started working. Along with the weird hashing of an empty string, this makes more more convinced it has something to do with this size setting. How has this config in the manifest not got a size? Is this really the problem? Is it something we've managed to drop in the intermediate registry, or has docker uploaded it incorrectly? I'd love any suggestions! -i

2 2

[zuul-ci.org] Update Freenode nics
by Jimmy McArthur 30 Aug '21

30 Aug '21

Hi all - I just noticed that the contact nics on the Governance page[1] are still the freenode nics. I'd update, but I'm not sure what to update it all to :) Cheers, Jimmy [1] https://zuul-ci.org/docs/zuul/reference/governance.html

4 4

Static nodes enter infinite 'building' state
by Vitaliy Lotorev 23 Aug '21

23 Aug '21

Hi, I'm using Zuul 4.7.0 and Nodepool 4.2.2. My nodes are all static. Now and then all nodes enter an infinite 'building' state. E.g. here is how building node 0000000113 starts (node_request: 300-0000000094): 2021-08-19 15:28:42,203 DEBUG nodepool.PoolWorker.static-vms-main: [e: 5a36f7ab18e54a11ad728fecab385be6] [node_request: 300-0000000094] Locking request 2021-08-19 15:28:42,219 INFO nodepool.PoolWorker.static-vms-main: [e: 5a36f7ab18e54a11ad728fecab385be6] [node_request: 300-0000000094] Assigning node request <NodeRequest {'state': 'requested', 'state_time': 1629386913.1936047, 'declined_by': [], 'node_types': ['centos7'], 'nodes': [], 'reuse': True, 'requestor': '79d78decd29a', 'requestor_data': {'build_set_uuid': '344e4dec0639481b85d62c0ab6efa0e9', 'tenant_name': 'nto7', 'pipeline_name': 'check', 'job_name': 'buildroot-build'}, 'provider': None, 'relative_priority': 0, 'event_id': '5a36f7ab18e54a11ad728fecab385be6', 'id': '300-0000000094', 'stat': ZnodeStat(czxid=209282, mzxid=209282, ctime=1629386913193, mtime=1629386913193, version=0, cversion=0, aversion=0, ephemeralOwner=72217169448337409, dataLength=400, numChildren=0, pzxid=209282)}> 2021-08-19 15:28:42,219 DEBUG nodepool.driver.NodeRequestHandler[9c4813b37c0b-PoolWorker.static-vms-main-aa0248e60f7d49c9b5065855fe7e0842]: [e: 5a36f7ab18e54a11ad728fecab385be6] [node_request: 300-0000000094] Accepting node request 2021-08-19 15:28:42,253 DEBUG nodepool.driver.NodeRequestHandler[9c4813b37c0b-PoolWorker.static-vms-main-aa0248e60f7d49c9b5065855fe7e0842]: [e: 5a36f7ab18e54a11ad728fecab385be6] [node_request: 300-0000000094] Locked building node 0000000113 for request 2021-08-19 15:28:42,276 DEBUG nodepool.driver.NodeRequestHandler[9c4813b37c0b-PoolWorker.static-vms-main-aa0248e60f7d49c9b5065855fe7e0842]: [e: 5a36f7ab18e54a11ad728fecab385be6] [node_request: 300-0000000094] Waiting for node 0000000113 to be ready 2021-08-19 15:28:42,277 DEBUG nodepool.PoolWorker.static-vms-main: Active requests: ['300-0000000078', '300-0000000079', '300-0000000080', '300-0000000081', '300-0000000082', '300-0000000083', '300-0000000084', '300-0000000085', '300-0000000086', '300-0000000087', '300-0000000088', '300-0000000089', '300-0000000090', '300-0000000091', '300-0000000092', '300-0000000093', '300-0000000094'] After two days node_request: 300-0000000094 still hanging in active requests (node 0000000113 is also seen in web UI in building state). To clean nodepool I have to restart nodepool once a week. Actually this issue has been tracing me for more than a year (so it's not something that appeared in the latest nodepool versions). I hoped recent commit [1] (included in nodepool 4.2.2) might be relevant to fixing my issue but it has not changed anything. [1] https://review.opendev.org/c/zuul/nodepool/+/790674 -- Regards, Vitaliy Lotorev

2 2

Zuul has moved from IRC to Matrix
by James E. Blair 21 Aug '21

21 Aug '21

Hi, The Zuul project has completed its move from IRC to Matrix. If you would like to chat with us, please join our room, #zuul:opendev.org -- you can follow this link for convenience: https://matrix.to/#/#zuul:opendev.org You can read detailed instructions on how to get started using Matrix (it's easy!) here: https://zuul-ci.org/docs/zuul/howtos/matrix.html Those instructions also include information on how to use Matrix to participate in bridged IRC channels, so you can use the same client to participate in communities that use IRC. If you are still in the IRC channel, please go ahead and /part in order to aid us in shutting it down. -Jim

1 0

Moving from IRC to Matrix
by James E. Blair 18 Aug '21

18 Aug '21

Hi, The Zuul community will be moving our official chat platform to Matrix on Saturday, August 21. The room has not been created yet, but when it is, the name will be #zuul:opendev.org We will update the website and instructions in the documentation accordingly over the next few days. Starting next week, we will no longer use the #zuul IRC channel on OFTC, and will encourage anyone remaining in that channel to /part. You don't need to do anything right now -- because Matrix preserves history, you can join the new room at any point in the future and have access to messages sent before you joined, so you won't miss anything by joining after the move. -Jim

1 0

Move to Matrix
by James E. Blair 17 Aug '21

17 Aug '21

Hi, It looks like the technical pre-requisites are in place for us to move from IRC to a native Matrix channel hosted by OpenDev. Thanks to everyone who helped get that set up! I'd like to propose that we move this Saturday, August 21. It's usually pretty quiet on the weekend. On that date, we will move the bots from the IRC channel to the Matrix room. Since the room history will be available to anyone who joins, you don't need to worry about missing anything by not joining ahead of time. We will create the room sometime on or before Saturday, and whenever you join, you'll see the history. After the cutover, some of us will remain in the IRC channel to inform anyone who might be unaware of the move. I imagine after a week or so of that, we will restrict access to the channel and depart for good. I encourage folks to /part from the IRC channel as soon as possible after the cutover. Does that sound good? -Jim

3 2

zuul/zuul-executor image Dockerfile
by Yaniv Levy 15 Aug '21

15 Aug '21

Hi, Where can I see the Dockerfile that is used to create "zuul/zuul-executor' image? In the source tree I can see zuul/.zuul.yaml and there is a job 'zuul-build-image' but I don't see how it actually builds the image I did 'sudo docker image inspect zuul-executor' in order to find what is the command line for the zuul/zuul-executor docker image > sudo docker image inspect zuul/zuul-executor "Cmd": [ "/usr/local/bin/zuul-executor", "-f" ], Thanks, Yaniv -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

3 3

'quickstart' help needed
by Yaniv Levy 11 Aug '21

11 Aug '21

Hi, I'm following the 'Quick-Start Installation and Tutorial'. Using centos 7. I've configured gerrit and the pipelines and it went well. At the point of "Test Zuul Pipelines", I have configured the test job for projects test1 playbooks/testjob.yaml and .zuul.yaml, When I commit these files to 'test1' project, the job test will fail and in gerrit review I see verified:-1 In the window where docker-compose runs, I see the log message the test fail executor_1 | 2021-08-10 08:52:39,772 INFO zuul.AnsibleJob: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Job execution took: 3.858 seconds scheduler_1 | 2021-08-10 08:52:39,777 INFO zuul.Scheduler: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Build complete, result FAILURE, warnings [] Where can I see why the test fails? Thanks Yaniv scheduler_1 | 2021-08-10 08:52:34,663 INFO zuul.GerritConnection: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Updating <Change 0x7f6154206df0 None 2,1> scheduler_1 | 2021-08-10 08:52:34,722 INFO zuul.Pipeline.example-tenant.check: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Adding change <Change 0x7f6154206df0 test1 2,1> to queue <ChangeQueue check: test1> in <Pipelin$ check> scheduler_1 | 2021-08-10 08:52:34,723 INFO zuul.Pipeline.example-tenant.check: Reporting enqueue, action [] item <QueueItem 940958dd98db44b68bbe21195c8b90da for <Change 0x7f6154206df0 test1 2,1> in check> executor_1 | 2021-08-10 08:52:34,739 INFO zuul.ExecutorServer: Updating repo gerrit/test1 executor_1 | 2021-08-10 08:52:34,740 INFO zuul.Merger: Updating local repository gerrit/test1 executor_1 | 2021-08-10 08:52:34,999 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Merge <MergeRequest f0b04276d3064dc984ae9ccb310af626, job_type=merge, state=running, path=/zuul/merger/request$ /f0b04276d3064dc984ae9ccb310af626> complete, merged: True, updated: False, commit: 340c1d864be76878dfda9b58a08ddeafbb7bf0fa, branches: [] scheduler_1 | 2021-08-10 08:52:35,037 INFO zuul.Pipeline.example-tenant.check: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Scheduling global repo state for item <QueueItem 940958dd98db44b68bbe21195c8b90da for <Change 0$ 7f6154206df0 test1 2,1> in check> executor_1 | 2021-08-10 08:52:35,151 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Merge <MergeRequest c36c1839119040e0abb03b1629af1fda, job_type=refstate, state=running, path=/zuul/merger/requ$ sts/c36c1839119040e0abb03b1629af1fda> complete, merged: False, updated: True, commit: None, branches: [] scheduler_1 | 2021-08-10 08:52:35,167 INFO zuul.nodepool: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Submitted node request <NodeRequest 200-0000000000 <NodeSet [<Node None ('ubuntu-focal',):ubuntu-focal>]>> launcher_1 | 2021-08-10 08:52:35,707 INFO nodepool.PoolWorker.static-vms-main: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [node_request: 200-0000000000] Assigning node request <NodeRequest {'state': 'requested', 'sta$ e_time': 1628585555.1663659, 'declined_by': [], 'node_types': ['ubuntu-focal'], 'nodes': [], 'reuse': True, 'requestor': '9790a3a8d89d', 'requestor_data': {'build_set_uuid': 'aeb144df01014a4fb29c13a2d557e78c', 'tenan$ _name': 'example-tenant', 'pipeline_name': 'check', 'job_name': 'testjob'}, 'provider': None, 'relative_priority': 0, 'event_id': 'ea31482e46dc49dc9e50f9c7e66bbe94', 'id': '200-0000000000', 'stat': ZnodeStat(czxid=73$ , mzxid=734, ctime=1628585555166, mtime=1628585555166, version=0, cversion=0, aversion=0, ephemeralOwner=73564082917998594, dataLength=399, numChildren=0, pzxid=734)}> scheduler_1 | 2021-08-10 08:52:35,716 INFO zuul.nodepool: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Node request <NodeRequest 200-0000000000 <NodeSet [<Node 0000000000 ('ubuntu-focal',):ubuntu-focal>]>> fulfilled scheduler_1 | 2021-08-10 08:52:35,727 INFO zuul.nodepool: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Accepting node request <NodeRequest 200-0000000000 <NodeSet [<Node 0000000000 ('ubuntu-focal',):ubuntu-focal>]>> scheduler_1 | 2021-08-10 08:52:35,728 INFO zuul.Pipeline.example-tenant.check: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Completed node request <NodeRequest 200-0000000000 <NodeSet [<Node 0000000000 ('ubuntu-focal',)$ ubuntu-focal>]>> for job testjob of item <QueueItem 940958dd98db44b68bbe21195c8b90da for <Change 0x7f6154206df0 test1 2,1> in check> with nodes <NodeSet [<Node 0000000000 ('ubuntu-focal',):ubuntu-focal>]> scheduler_1 | 2021-08-10 08:52:35,730 INFO zuul.ExecutorClient: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Execute job testjob (uuid: 46d7d5a1c1ae4ba8b8497bf128662c94) on nodes <NodeSet [<Node 0000000000 ('ubuntu-foca$ ',):ubuntu-focal>]> for change <Change 0x7f6154206df0 test1 2,1> with dependent changes [{'project': {'name': 'test1', 'short_name': 'test1', 'canonical_hostname': 'gerrit', 'canonical_name': 'gerrit/test1', 'src_dir$ : 'src/gerrit/test1'}, 'branch': 'master', 'change': '2', 'change_url': ' http://gerrit:8080/2', 'patchset': '1'}] executor_1 | 2021-08-10 08:52:35,903 INFO zuul.ansible_manager: Ansible version 2.9 ARA callback plugin: /usr/local/lib/zuul/ansible/2.9/lib/python3.8/site-packages/ara/plugins/callbacks executor_1 | 2021-08-10 08:52:35,917 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Started SSH Agent, {'SSH_AUTH_SOCK': '/tmp/ssh-OjvHlbQ9zfiC/agent.12$ 3', 'SSH_AGENT_PID': '1254'} executor_1 | 2021-08-10 08:52:35,929 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Added SSH Key /var/ssh/nodepool executor_1 | 2021-08-10 08:52:35,934 INFO zuul.AnsibleJob: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Beginning job testjob for ref refs/changes/02/2/1 (change http://gerrit:$ 080/2) executor_1 | 2021-08-10 08:52:35,934 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Updating repo gerrit/test1 executor_1 | 2021-08-10 08:52:35,934 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Updating repo gerrit/zuul-config executor_1 | 2021-08-10 08:52:35,946 INFO zuul.Merger: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Skipping updating local repository gerrit/zuul-config executor_1 | 2021-08-10 08:52:35,949 INFO zuul.Merger: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Skipping updating local repository gerrit/test1 executor_1 | 2021-08-10 08:52:37,720 INFO zuul.AnsibleJob: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Checking out gerrit/test1 zuul branch master executor_1 | 2021-08-10 08:52:37,752 INFO zuul.nodepool: Setting nodeset <NodeSet [<Node 0000000000 ['ubuntu-focal']:ubuntu-focal>]> in use executor_1 | 2021-08-10 08:52:37,755 INFO zuul.AnsibleJob: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Checking out gerrit/test1 branch master executor_1 | 2021-08-10 08:52:37,807 INFO zuul.AnsibleJob: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Checking out gerrit/zuul-config branch master executor_1 | 2021-08-10 08:52:39,763 INFO zuul.ExecutorServer: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Held status set to False executor_1 | 2021-08-10 08:52:39,771 INFO zuul.nodepool: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Returning nodeset <NodeSet [<Node 0000000000 ['ubuntu-focal']:ubuntu-focal>]> executor_1 | 2021-08-10 08:52:39,772 INFO zuul.nodepool: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Nodeset <NodeSet [<Node 0000000000 ['ubuntu-focal']:ubuntu-focal>]> with 1 nodes was in use for 3.857801016420126 se$ onds for build <zuul.executor.server.AnsibleJob object at 0x7f33906607f0> for project gerrit/test1 executor_1 | 2021-08-10 08:52:39,772 INFO zuul.AnsibleJob: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Job execution took: 3.858 seconds scheduler_1 | 2021-08-10 08:52:39,777 INFO zuul.Scheduler: [e: ea31482e46dc49dc9e50f9c7e66bbe94] [build: 46d7d5a1c1ae4ba8b8497bf128662c94] Build complete, result FAILURE, warnings [] scheduler_1 | 2021-08-10 08:52:39,795 INFO zuul.Pipeline.example-tenant.check: [e: ea31482e46dc49dc9e50f9c7e66bbe94] Reporting item <QueueItem 940958dd98db44b68bbe21195c8b90da for <Change 0x7f6154206df0 test1 2,1$ in check>, actions: [<zuul.driver.gerrit.gerritreporter.GerritReporter object at 0x7f615423aa30>] gerrit_1 | [2021-08-10T08:52:40.357Z] [SendEmail-1[java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@57127397[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@7cdd90cd [Wr$ pped task = com.google.gerrit.server.logging.LoggingContextAwareRunnable@705fb592]]]] ERROR com.google.gerrit.server.change.EmailReviewComments : Cannot email comments for 2,1 [CONTEXT project="test1" ] gerrit_1 | com.google.gerrit.exceptions.EmailException: Mail Error: Connection refused (Connection refused) -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

2 6

Using React Hooks for the Zuul web UI
by Tristan Cacqueray 05 Aug '21

05 Aug '21

Hi, This is a thread to discuss using React Hooks for the web interface. The main motivation is described in: https://reactjs.org/docs/hooks-intro.html#motivation For Zuul that means we could break the redux store into a per page reducer hook which should simplify a lot the existing code base. To achieve that we would need to modify the existing class based component into function. The good news is that we can do that incrementally, component by component. I recently did such refactor for an application similar to zuul web interface with great success and I would be happy to help with such effort. Regards, -Tristan

4 20

Disable anchor and alias in inventory.yaml
by Dong.Zhang＠bmw.de 05 Aug '21

05 Aug '21

One of our zuul user suggested to disable anchor and alias in inventory.yaml to increase the readability. The inventory.yaml meant to be read by human, und it is not convenient when there are anchors and alias, that you need always search in the file back and forth for them. I am aware that disabling it might introduce some duplicate content. How ever since it would be unlikely the amount of content is big, and it would increase the readability, it would be worth to do it. Before I proceed, I would also like to hear others’ opinions. If you see there are some other important reasons not do that, please let me know. Best Regards, Dong Zhang

1 0

Diversity and Inclusion Meeting Reminder - OFTC
by Amy Marrich 01 Aug '21

01 Aug '21

The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Monday Auguat 2nd, at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (apotz)

1 0

Re: Zuul 4.7.0 released
by Paul Belanger 31 Jul '21

31 Jul '21

On Thu, Jul 29, 2021 at 04:37:59PM -0700, James E. Blair wrote: > The Zuul team is pleased to announce the release of Zuul 4.7.0. > > Download it from PyPI: https://pypi.org/project/zuul > > Find container images at: https://hub.docker.com/u/zuul > > The release notes, included below, are also available in the > documentation with hyperlink references: > > https://zuul-ci.org/docs/zuul/4.7.0/reference/releasenotes.html > > ... We managed to upgrade today to 4.7.0 but noticed something new: 2021-07-31 14:29:47,287 ERROR zuul.Scheduler: Error starting Zuul: Traceback (most recent call last): File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/cmd/scheduler.py", line 152, in run self.sched.prime(self.config) File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/scheduler.py", line 636, in prime self._doReconfigureEvent(event) File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/scheduler.py", line 945, in _doReconfigureEvent min_ltimes=min_ltimes) File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/configloader.py", line 2358, in loadTenant abide, unparsed_config, ansible_manager, min_ltimes) File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/configloader.py", line 1572, in fromYaml tenant.addUntrustedProject(tpc) File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/model.py", line 5374, in addUntrustedProject self._addProject(tpc) File "/opt/venv/zuul-4.7.0/lib/python3.6/site-packages/zuul/model.py", line 5256, in _addProject (project,)) Exception: Project ansible-collections/kubernetes.core is already in project index I haven't tried to debug why yet, however 16 days ago we added the duplicate project to our tenant config: https://github.com/ansible/project-config/pull/870 Currently we do not run any sort of tenant validatation for duplicate projects, but will update our linters to check. Before I go out an write a bunch of linter code, how do others deal with this? I don't believe anything changes zuul side (could be wrong) to enforce this. But also know zuul won't dynamically load this config (like pipeline config) to warn the user too. We are allowing more non-zuul folks the ability to add new projects into our tenant but they don't have root access to the scheduler so would like to help catch most of these things before we land the changes. Thanks, Paul

2 2

Removal of ansible_connection, etc. for 4.6
by Kenny Ho 20 Jul '21

20 Jul '21

Hi, Per the release log, "connection-related variables are no longer allowed to be set in job definitions, as they may be used to circumvent security measures." Does this apply to both untrusted-projects and config-projects or does it only apply to untrusted-projects? Regards, Kenny

3 3

Recommendation for logs rotation service
by Vitaliy Lotorev 15 Jul '21

15 Jul '21

Hi, Zuul requires external storage for logs and I failed to find a simple solution for removing jobs log directories after a period of time. What I've found so far: * zuul.opendev.org uploads logs to AFS and Swift. Looking at https://opendev.org/opendev/system-config/ I can't understand how directories are rotated on AFS. * probably Swift has built-in file/logs rotation, but I don't have OpenStack and Swift. * free Aftifactory CE/OSS version doesn't support plugins which are recommended to implement cron cleanup plugin https://jfrog.com/knowledge-base/artifactory-cleanup-best-practices/ Could you help with ideas for in-house OSS storage service that would cleanup directories with binary artifacts/logs? In case of logs kept on AFS zuul.opendev.org: are directories cleaned up just by date (e.g. remove all 'check jobs after two weeks')? -- Regards, Vitaliy

3 3

Take care when deleting email addresses in Gerrit
by Clark Boylan 14 Jul '21

14 Jul '21

Hello everyone, We have discovered a bug in Gerrit [0] that allows you to delete your account's Ubuntu One OpenID association if you delete the email from your account associated with that OpenID. When you do this the next time you log in Gerrit will create a new account for you. Fixing this after the fact is currently difficult. We are working to correct this but the required corrections take time. We would like to avoid these issues in the first place. Please avoid deleting email addresses from your accounts unless you are sure they are not associated with your OpenID. If you would like help double checking that for you please let us know and one of our Gerrit admins can double check. We are working to make this fixable after the fact, and will try to work with the Gerrit upstream to prevent you from deleting Ubuntu One OpenID associations from your account in the first place. Until then we apologize for the inconvenience. Finally, this message and others like it are sent to service-announce(a)lists.opendev.org. I am sending this email to a much broader set of mailing lists because the service-announce list membership is quite small. All of our users should be subscribed to that list to get important notices like this one. We keep the traffic low and only send mail there when we feel it is important for you to see it. [0] https://bugs.chromium.org/p/gerrit/issues/detail?id=14776 Clark

1 0

review.opendev.org server upgrade 18/19th July 2021
by Ian Wienand 13 Jul '21

13 Jul '21

Hello, Around 2021-07-18 23:00 UTC we plan to provision an upgrade to the review.opendev.org server which hosts our Gerrit instance. We are aware that some users may require firewall updates or similar to access the new server. The new addresses will be: 199.204.45.33 2604:e100:1:0:f816:3eff:fe52:22de We hope the downtime will be limited to a few hours as we migrate and index the data. User-visible changes be should minimal. Due to incompatible schemas between the old hosted database and new database instance we will not be transitioning the table that holds the information about what files you have reviewed (gerrit shows a light-grey "Reviewed" when you have viewed a file). Note this is *not* review comments or code, but just the per-user flag in the UI if you have viewed a file. You can reach admins via email at service-discuss(a)lists.opendev.org or in OFTC #opendev for any further questions or queries. Thank you, -i

1 1

Running Zuul under docker compose demo with GitLab connection
by Maxim Afanasyev 13 Jul '21

13 Jul '21

Hello We would like to try Zuul CI in our organization, because we already had very positive experience of configuring jobs in one of projects for our partner company. But in that case Zuul was installed on different hosting, by different team and used GitHub connection. Thus we want to setup it on our own and load all projects by using GitLab driver. To start, we followed these tutorials and sample configurations: https://zuul-ci.org/docs/zuul/tutorials/quick-start.html Quick-Start Installation and Tutorial — Zuul documentation<https://zuul-ci.org/docs/zuul/tutorials/quick-start.html> Quick-Start Installation and Tutorial¶. Zuul is not like other CI or CD systems. It is a project gating system designed to assist developers in taking a change from proposal through deployment. zuul-ci.org https://zuul-ci.org/docs/zuul/reference/drivers/gitlab.html GitLab — Zuul documentation<https://zuul-ci.org/docs/zuul/reference/drivers/gitlab.html> This indicates that changes originating from the GitLab connection must be in the opened state (not merged yet).. pipeline.require.<gitlab source> ¶. The dictionary passed to the GitLab pipeline require attribute supports the following attributes:. pipeline.require.<gitlab source>. open ¶. A boolean value (true or false) that indicates whether the Merge Request must be open in order to be ... zuul-ci.org https://gist.github.com/mpiscaer/2e731c8becea781c4521cc15b5cfeabe and took the sample based on the docker compose (version around 21.05.2021) GitLab driver basically works, but we faced the following issues: 1) SSL certificate verification. By default Zuul did not accept certificates of our GitLab server and unfortunately the adding of public keys under "certs" did not help. The workaround was to add line: self.session.verify = False into the "init" method of "GitlabAPIClient" The question: is it possible to add some option to disable such check in the GitLab driver configuration? 2) API works only partially For example the request to http://ubuntu2:9000/api/tenants in Firefox gives JSON response with list of configured tenants and headers are: Access-Control-Allow-Origin * Content-Length 44 Content-Type application/json; charset=utf-8 Date Tue, 06 Jul 2021 21:33:34 GMT Server CherryPy/18.6.0 but if I call the same URL via "curl" or in Google Chrome, then the webpage is displayed with request to enable Javascript and headers are: Accept-Ranges: bytes Content-Length: 2230 Content-Type: text/html;charset=utf-8 Date: Tue, 06 Jul 2021 21:40:58 GMT Last-Modified: Thu, 20 May 2021 10:56:25 GMT Server: CherryPy/18.6.0 ............. <noscript>You need to enable JavaScript to run this app.</noscript> .............. The question: why can it happen, does it depend on request content and headers? I suppose because of this we cannot use webhooks to run jobs triggered by GitLab pushes (actually also HTML page is returned) Thank you in advance Best Regards Maxim Afanasyev Software Developer test frameworks / SWBK mob: + 49 (176) 35-42-55-24

3 2

Debugging non-starting periodic jobs; probably since 4.6.0
by Ian Wienand 06 Jul '21

06 Jul '21

Hi, I've been trying to debug why release-wheel-cache https://zuul.opendev.org/t/openstack/builds?job_name=release-wheel-cache doesn't seem to have run since 2021-06-27. I don't believe we've made any changes to these jobs, but I think Zuul has deployed quite a bit of change. The build-wheel-cache jobs are in openstack-zuul-jobs [1]. We then have publish-wheel-cache jobs [2] that are children of these jobs and essentially wrap the build jobs with "get afs token, write wheels to afs" wrappers. These jobs are in the periodic pipeline of the requirements project via project-config [3]. Finally the release-wheel-cache (also [3]) runs after all the publish-wheel-cache-* jobs to "vos release" the various wheel volumes. Note it seems none of the individual jobs (publish-wheel-cache-*) has run since 2021-06-27 either, but I've just concentrated on release-wheel-cache as it depends on all the others. I believe the last time it ran has been captured in [4] starting at 2021-06-27 06:00:35,268 DEBUG zuul.Scheduler: [e:963101cc7c01460abfd34664e5610e18] Forwarding trigger event <TimerTriggerEvent 0x7fe33db4fa00 timer openstack/requirements refs/heads/master> This is the last result we see in the build log. The next time it tries is [5] at 2021-06-28 06:00:17,437 DEBUG zuul.Scheduler: [e:afdb7039494649c09e8bb2b64158a385] Forwarding trigger event <TimerTriggerEvent 0x7fe3424015e0 timer openstack/requirements refs/heads/master> I think the interesting thing here is that this seems to go into a tight loop of 2021-06-28 06:08:34,701 DEBUG zuul.Pipeline.openstack.periodic: [e: afdb7039494649c09e8bb2b64158a385] Checking for changes needed by <Branch 0x7fe343803e50 openstack/requirements refs/heads/master updated None..None>: 2021-06-28 06:08:34,701 DEBUG zuul.Pipeline.openstack.periodic: [e: afdb7039494649c09e8bb2b64158a385] <class 'zuul.model.Branch'> does not support dependencies ... 2021-07-02 14:20:30,699 DEBUG zuul.Pipeline.openstack.periodic: [e: afdb7039494649c09e8bb2b64158a385] Checking for changes needed by <Branch 0x7fe343803e50 openstack/requirements refs/heads/master updated None..None>: 2021-07-02 14:20:30,700 DEBUG zuul.Pipeline.openstack.periodic: [e: afdb7039494649c09e8bb2b64158a385] <class 'zuul.model.Branch'> does not support dependencies every few seconds for the next few days; I think until restarted Zuul at @ 2021-07-02 14:22:33 according to logs at [6] (it stops at 14:20) So then the latest run is triggered at [7] 2021-07-05 06:00:13,771 DEBUG zuul.Scheduler: [e: 5fe4dd08d1a44700bf92fd475565f687] Forwarding trigger event <TimerTriggerEvent 0x7fa02c8d62e0 timer openstack/requirements refs/heads/master> but nothing seems to run. Further complicating things, I know the requirements project had some config errors from the recent security fixes until about 2021-06-28 [8]. So far I'm at a bit of a loss to correlate all this into a coherent story. Hopefully some other eyes might see what I'm missing! Thanks, -i [1] https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/… [2] https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.… [3] https://opendev.org/openstack/project-config/src/branch/master/zuul.d/proje… [4] http://people.redhat.com/~iwienand/zuul-periodic-27-06-2021/963101cc7c01460… [5] http://people.redhat.com/~iwienand/zuul-periodic-27-06-2021/afdb7039494649c… [6] https://wiki.openstack.org/wiki/Infrastructure_Status [7] http://people.redhat.com/~iwienand/zuul-periodic-27-06-2021/5fe4dd08d1a4470… [8] https://review.opendev.org/c/openstack/requirements/+/798361

1 1

Gerrit master branch is always required?
by Vitaliy Lotorev 01 Jul '21

01 Jul '21

Hi, 1. We have 'linux/kernel' repo (with Linux kernel) with 'upstream' (tracks upsteam), 'projectA', 'projectB'. This repo didn't have 'master' branch as it didn't make sense for repo owners and users (upst. Once I create commit that depends-on commit to linux/kernel then Zuul reports an error 'failed to load configuration from linux/kernel' as the 'master' branch doesn't exist. We had to create master branch in this and other repos that have an upstream project. 2. In git world there is tendency to switch from 'master' to 'main' branch (Gerrit 3.4 introduced host-level defaultbranch config [1], Gitlab announcement for main branch [2]). Even if we would set defaultbranch to 'main' we still need to create 'master' branch? Am I correct that Zuul currently doesn't support repos without a 'master' branch? [1] https://gerrit-review.googlesource.com/Documentation/config-gerrit.html#ger… [2] https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/ ---- Regards, Vitaliy

2 2

[Diversity] Diversity and Inclusion July Meeting Update
by Amy Marrich 30 Jun '21

30 Jun '21

Due to most US companies having July 5th off, we will be moving the Jully D&I WG meeting Please join us Monday, July 19th at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Thanks, Amy (spotz)

1 0

Representation at Ansiblefest?
by Jeremy Stanley 22 Jun '21

22 Jun '21

As David mentioned earlier today in #zuul, the CFP[*] for Ansiblefest[**] closes in one week. In the past there have been a number of great 'Fest talks on and related to Zuul as well as Zuul contributors/users in attendance. Is anyone submitting a Zuulish talk this year? [*] https://reg.rainfocus.com/flow/redhat/ansible21/cfp [**] https://www.ansible.com/ansiblefest -- Jeremy Stanley

1 0

lockstep of nodepool / zuul
by Paul Belanger 22 Jun '21

22 Jun '21

Hi, Looking for confirmation, because there is no direct dependency between nodepool and zuul, there is no need to lockstep the 4.0 releases of each right? I'd like to upgrade nodepool first, to confirm TLS is setup propelry, then deal with zuul. Thanks, Paul

2 1

Proposal: gating.dev website
by James E. Blair 16 Jun '21

16 Jun '21

Hi, I have a domain name, gating.dev, that I'd like to turn over to the Zuul community/OIF, if we're interested. Here's my vision for it: * A one-page site that explains/promotes the concept of project gating. * It's not immediately focused on Zuul; if the word "Zuul" shows up, it's probably at the bottom. * Currently, when we talk to people about Zuul and project gating, they don't immediately "get it". We should be able to direct people to this site, and in short order, they should "get it" (ideally, they should want it, but at the least, they should understand it). * The simple URL makes it easy to remember and casually drop into conversations (e.g., twitter threads, etc). * It's not super complex. It's maybe not the place to explain the NNFI or Tarjan's algorithms. * Clear, direct text with images. I think there are folks in this community that can contribute to this far better than I can. I may be kicking this off, but if we relied on me to write the text/images, we'd just end up with another copy of the reference manual, so don't do that. :) Just to try to communicate the framework I'm thinking -- maybe a "hero" sentence at the top to set the stage, then maybe one of those things where there's a row of 3 benefits with nice graphics, then under that there's more text... I just described the Zuul website, so... we could use that structure -- it seems to work for a lot of folks, or maybe someone has an actual different idea. ;) Okay, that's enough rambling from me. Do folks like this idea? Any suggestions to get started? Maybe we can brainstorm here for a bit and if it sounds like the idea has legs, we can set up a new repo for it. -Jim

6 5

Zookeeper and SSL
by Paul Belanger 15 Jun '21

15 Jun '21

Hi! So, I am in the process of enabling SSL on our instance of Zuul and a little surprised to see that no version of Zookeeper in debubuntu repos actually support SSL. The installation docs for Zuul, don't seem to reference how to install zookeeper, expect installing the version that doesn't support SSL. How are others doing this? Does anyone know of an existing PPA to pull zookeeper from? Paul

5 6

Re: Upcoming security release
by James E. Blair 10 Jun '21

10 Jun '21

I just sent the following message to zuul-announce: On 6/10/21 8:59 AM, James E. Blair wrote: > Multiple security issues have been identified in Zuul which could lead > to an exposure of secret data. The Zuul Maintainers have been preparing > fixes to these issues and plan to make a release of Zuul with them on > Thursday, June 24, 2021, around 14:00 UTC. > > Unfortunately, there is no known mitigation for these vulnerabilities, > and so the best advice we can offer for operators is to stop Zuul > shortly before the release, and restart it after updating. > > Additionally, there will be some modification to the functionality > offered by Zuul, which may cause some jobs to fail or behave > differently. More details will be provided along with the release. > > We encourage you to use the time between now and June 24th to ensure > that you are running the latest version of Zuul (4.5.0) in order to > prepare for the update. > > An announcement of the release and accompanying information will be sent > to zuul-announce(a)lists.zuul-ci.org when the release is available. > > Feel free to follow up to zuul-discuss(a)lists.zuul-ci.org or chat with us > in #zuul on OFTC if you have any questions. > In light of that, I think we should consider Zuul development mostly frozen until the release. Please continue to upload and review changes, but let's avoid merging significant functional changes, and limit merges to bugfixes, doc updates, etc. This will provide a stable platform for people to upgrade from 4.5.0 to the upcoming release. Meanwhile, we can continue to +2 changes and stack them up (either as git dependencies or using depends-on) to resume development after the release. -Jim

2 1

AWS driver for Nodepool IAM policies
by Fabien Boucher 08 Jun '21

08 Jun '21

Hi, We plan to use the AWS driver for Nodepool but looking at the documentation [1] it is not clear which IAM policies we need to configure for the Nodepool account. If some of you have experience with the AWS driver could it be possible to share some details about the policy setup for the Nodepool user ? For instance, which actions must be allowed [2] ? Fabien [1]: https://zuul-ci.org/docs/nodepool/aws.html [2]: https://docs.aws.amazon.com/service-authorization/latest/reference/list_ama…

1 0

file sync issue?
by Åsmund Østvold 08 Jun '21

08 Jun '21

Hi, I suddenly experience: 2021-06-08 07:59:39.647866 | 2021-06-08 07:59:39.870542 | PRE-RUN END RESULT_NORMAL: [trusted : review.resoptima.net/zuul/irma_config/playbooks/base/pre.yaml@master] 2021-06-08 07:59:39.870861 | RUN START: [trusted : review.resoptima.net/zuul/irma-common-jobs/playbooks/build_and_integrationt…] 2021-06-08 07:59:41.191318 | 2021-06-08 07:59:41.191500 | PLAY [Role run build.sh] 2021-06-08 07:59:41.228238 | 2021-06-08 07:59:41.228438 | TASK [buildsh.zuul : runs-build.sh-in-folder] 2021-06-08 08:00:45.088247 | ubuntu-bionic | + hostname 2021-06-08 08:00:45.088748 | ubuntu-bionic | stenant01 2021-06-08 08:00:45.088788 | ubuntu-bionic | + cd src/review.resoptima.net/zuul/irma-common-jobs 2021-06-08 08:00:45.088797 | ubuntu-bionic | + ../../resoptima/tools/automation/cleanup_and_setup.sh 2021-06-08 08:00:45.089124 | ubuntu-bionic | /bin/sh: 5: ../../resoptima/tools/automation/cleanup_and_setup.sh: not found I have sufficient disk on the node. Any idea what could be wrong? Cheers, Åsmund

1 1

Last call on two specs
by James E. Blair 04 Jun '21

04 Jun '21

Hi, The following specs have undergone several review cycles and I think they may be in or near their final state. I'd encourage anyone with an interest to review these and leave feedback. Zuul Maintainers, I'd like to merge these in a little over one week, on June 11, if there are no significant objections noted in review. If you need more time, please leave a review message to that effect, and we can extend the deadline. * Add spec for enhanced regional executor distribution https://review.opendev.org/663413 * Add Spec on Resource Quota per Tenant https://review.opendev.org/788481 -Jim

1 1

[Diversity] Diversity and Inclusion Meeting Reminder - OFTC
by Amy Marrich 04 Jun '21

04 Jun '21

The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Monday June 7th, at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (spotz)

1 0

stage-output role
by James E. Blair 31 May '21

31 May '21

Hi, A while back we had the idea that something like 'stage-output' could be put in a base job post-run playbook, and then users of any job could collect log files by just adding zuul job variables. However, that role has "become: true" set for three tasks (of primary importance: being able to copy system logs) and there are jobs in zuul-jobs which drop sudo at the start of the job. It seems difficult to reconcile these two ideas. Should we add some sort of detection in the stage-output role that is basically: if sudo is available, set become: true for those tasks, otherwise don't? Or should we remove become: true from those tasks and ask users to set become on the entire role invocation if they need it? -Jim

1 1

Possible use of Matrix?
by James E. Blair 29 May '21

29 May '21

Hi, I'm starting this as a new thread to clearly differentiate it from the short term question of "if we evacuate from freenode, where should we go?". I think moving to a different IRC network is important to do in the short term, and I don't want to confuse the issues. At the same time, this whole process has sparked a lot of discussion (mostly elsewhere) about alternative technologies. One that I think shows particular promise is Matrix, and I'd like to find out if other folks feel similarly. Some quick relevant points about Matrix (you can google it for more :): * It's a decentralized chat protocol, so no single entity controls the infrastructure running it. * It is truly open-source and a variety of client interfaces exist. * It optionally supports end-to-end encryption. * There are existing bridges to other communication networks, like Freenode, OFTC. Libera should arrive soon[1]. * A variety of community, outsourced, or self-hosted options exist. * A number of large and small open-source communities use it. Regarding the clients, I'd like to highlight three options: 1) There is a robust plugin for weechat (matrix-weechat). That means folks like me who like to have a small terminal window open for all of their messaging needs can seamlessly transition to using Matrix. 2) There is a very nice webclient (called Element) that looks and behaves like all the other really nice web chat clients; so folks who like user interfaces from this century can dig it. 3) There are mobile clients as well. In all cases, due to the way Matrix works, users can switch between clients or use multiple clients simultaneously, and all of these clients have access to channel history even when disconnected. This is perhaps one of the largest pain points for new users of IRC. The reason that works is that every user (and room) belongs to a "homeserver" and the homeserver handles storing messages and serving them to clients. Homeservers federate with other homeservers to form the larger Matrix network. Any user on any homeserver can talk to any other user or join any room on any other homeserver (assuming permission is granted). Typically, users do not run their own homeservers (unless they are enthusiasts -- the sort of folks who run their own email or web servers). Instead, they would either use a homeserver run by their company, or a project, or use the main public server hosted by the foundation which supports Matrix development: matrix.org. In short, this provides an ideal experience: * No need to run their own infrastructure * Federated, open-source, open protocols (no vendor lock-in) * Ability to communicate with many chat networks at once * Modern UX using more corporate-firewall-friendly connectivity options When you combine this with the IRC bridging support, Matrix makes an ideal interface to all of the IRC networks in addition to the Matrix itself. Okay, here's my vision for the future: First, I'd like to suggest that folks sign up for a matrix.org account and use the IRC bridge to connect to #zuul on freenode. If/when we switch to a different IRC network, just follow us to that network. This is an easy way for us to evaluate Matrix (both the clients and the server network) and decide if we like the technology. Assuming we do, then we should consider eliminating the middle-man, and move from a bridged IRC channel to a native Matrix room. At that point, we will want a homeserver for the room at least. This is where getting feedback early so that we know what to prepare for would be good (do we want a homeserver just to host rooms? or should we also be looking to host user accounts as well?). There are discussions to be had with OpenDev and the Foundation about this, but first we need to know where we want to go. If this sounds like a terrible idea, please let me know. If it sounds worth exploring, then I encourage you to do what I'm doing right now: use Matrix to interact with #zuul on IRC instead of a native IRC client. Try it out and let's see how it works. Here's what you do: 1) Go to https://app.element.io/ and sign up for an account. You know the drill. 2) Once you're logged in, click on the "+" next to "Rooms" and then "Explore public rooms". 3) Under the search bar where it says "Matrix rooms (matrix.org)" click the drop-down and switch it to "Freenode". Type "#zuul" into the search box. Click Join. 4) Now, ideally this would be the end of the instructions, and if we move to OFTC, hopefully it will be; but because of the spam problem on freenode, #zuul requires nick registration. That means we need to tell the matrix.org IRC bridge to use our registered nicks. You'll note that you have been kicked from #zuul and you have an invitation to join a room "Freenode IRC Bridge status". Accept the invitation. 5) Type "!help" to see a list of commands. 6) Type "!nick" followed by your existing Freenode nick. 7) Type "!storepass" followed by the password for your Freenode nick. Note, you're giving your nick password to a bot run by a third party. You'll need to evaluate whether you're okay with that. At the least, use a unique password. 8) Type "!join #zuul" (that should have the same effect as adding the room earlier). I admit, these instructions are weird since I told you to start by doing something that won't work. But I do want to show how simple this should be once we can either relax the nick registration requirement or move off of IRC completely; either way, it's just the first 3 steps. If you want to skip that part, you could initiate a PM to "@appservice-irc:matrix.org" and start at step #5. Each IRC bridge has a different bot running it; to do the same thing for OFTC, you would talk to "@oftc-irc:matrix.org". That's it for now. Please let me know if you have any feedback, and I'd encourage everyone to at least try out element/matrix. I've been using a lot of different chat systems lately, and I'm really pleased with how this is working out. Even if we decide to stay on IRC, I plan to use the Matrix bridge as my primary interface. If you do too, then it will be easy to stay connected with projects on various IRC networks as well as be prepared for any potential moves to Matrix. -Jim [1] https://github.com/matrix-org/matrix-appservice-irc/issues/1324

4 5

OpenDev IRC services are moving to OFTC this weekend
by Jeremy Stanley 26 May '21

26 May '21

As a majority of our constituent projects have voiced a preference for enacting our long-standing evacuation plan, the OpenDev Collaboratory's IRC service bots will be switching from Freenode to the OFTC network this weekend (May 29-30, 2021). We understand this is short notice, but multiple projects have requested that we act quickly. Please expect some gaps in channel logging and notifications from our various bots over the course of the weekend. I have provided a much more detailed writeup to the service-discuss mailing list, and encourage anyone with questions to read it and follow up there if needed. Subsequent updates will be sent only to service-discuss, in order to limit noise for individual project lists and keep further discussion focused in one place as much as possible: http://lists.opendev.org/pipermail/service-discuss/2021-May/000249.html -- Jeremy Stanley

2 1

OpenInfra Live - May 27 at 9am CT (1400 UTC)
by Erin Disney 26 May '21

26 May '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the Zuul community! Episode: Large Scale Open Source CI Featuring Zuul Date and time: May 27 at 9am CT (1400 UTC) Don’t merge broken code. Infrastructure at scale relies on quality software that is tested before it’s deployed. Operators rely on open source CI systems like Zuul for gating, scaling across organizations and cross-project dependencies. In this OpenInfra Live episode, Jim Blair, Zuul Maintainer and CEO at Acme Gating, and Mohammed Naser, CEO of Vexxhost will provide an overview of Zuul, the open source CI/CD business case and a demo showing what cross project dependencies looks like in production. You can watch us live on: YouTube: https://www.youtube.com/watch?v=yf5iFiCg_Tw <https://www.youtube.com/watch?v=yf5iFiCg_Tw> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6798703707925168128/ <https://www.linkedin.com/feed/update/urn:li:ugcPost:6798703707925168128/> Facebook: https://www.facebook.com/104139126308032/posts/3974109482644291/ <https://www.facebook.com/104139126308032/posts/3974109482644291/> WeChat: recording will be posted on OpenStack WeChat after the live stream Thanks, Erin Erin Disney Event Marketing Open Infrastructure Foundation

1 0

Pipeline run on Gerrit trigger change merge event
by Sankar Palanivel 26 May '21

26 May '21

Hi, We have configured 2 gerrit connections in zuul. We are expecting to have a zuul job of gerrit connection-01 should triggered based on the "change merge" events from gerrit connection-02. Is it even possible to configure in zuul? If so, can you please suggest a way to proceed? Thanks, Sankar Palanivel

2 9