- Zuul-discuss - lists.opendev.org

Zuul-runner spec
by corvus＠inaugust.com 03 Dec '20

03 Dec '20

Hi Zuul Maintainers, The zuul-runner spec[1] has gone through quite a bit of review and changes and is ready for us to make a final determination. I would appreciate it if all interested maintainers would take a look and leave a vote by December 11; we'll merge it if there are no objections by then. If you need more time to review, please say so and we can defer. [1] https://review.opendev.org/c/zuul/zuul/+/681277 Thanks, Jim

1 0

Improving "This change or one of its cross-repo dependencies was unable ..." message
by Fabien Boucher 30 Nov '20

30 Nov '20

Hi, I'd like to get your feeling about this error message that Zuul reports to end users: A user of Fedora Zuul CI, raised a concern about it. --- Merge Failed. This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset. --- I've attempted to explain it like this: --- This is a PR, so the content of <the-branch> is going to be merged (or rebased) onto the <target-branch>. Thus, Zuul tried it and reported that this change cannot be merged with the current state of the repository. This un-mergeable state makes Zuul stop processing and not run the jobs. --- The user raised that comment: --- Why it cannot say at least something like: "Attempt to rebase on top of master failed. This repository is not in a mergeable state". Why does it say "Merge failed", when it does not provide any context at all. Why does it mention "cross-repo dependencies" without any reference? --- It seems that the "Merge Failed" is ambiguous because it can be interpreted as "the final merge of the PR to the target branch". The user's proposal seems better. I think this "This change or one of its cross-repo dependencies" should be improved to give the repositories names that were unable to be "merged". Let me know what you think, I'll be happy to provide a change to Zuul to update this error message. Fabien

2 1

Question about integration with gerrit
by Rikimaru Honjo 25 Nov '20

25 Nov '20

Hi, I have a zuul instance in my environment. It is integrated with review.opendev.org as a 3rd party CI. It fails to post comment recently. There aren't error messages in log files. It used to be successful to post. My zuul version is 3.10.1. Should I upgrade it? I already checked release notes of zuul. But there aren't descriptions about it. Zuul-executor's log about posting comment: 2020-11-24 12:05:23,547 DEBUG zuul.AnsibleJob: [e: 6304c4d6a2a047b8ba2e05abf4b2907f] [build: 094b3be9dea64b1ead6a49886cf04cf2] Ansible complete, result RESULT_NORMAL code 0 2020-11-24 12:05:23,548 DEBUG zuul.AnsibleJob: [e: 6304c4d6a2a047b8ba2e05abf4b2907f] [build: 094b3be9dea64b1ead6a49886cf04cf2] Sending result: {"warnings": [], "data": {"zuul": {"log_url": "http://153.156.76.189:8000/641174/13/20201124110905"}}, "result": "SUCCESS"} 2020-11-24 12:05:23,571 DEBUG zuul.ExecutorServer: [e: 6304c4d6a2a047b8ba2e05abf4b2907f] [build: 094b3be9dea64b1ead6a49886cf04cf2] Sent SIGTERM to SSH Agent, {'SSH_AGENT_PID': '22823', 'SSH_AUTH_SOCK': '/tmp/ssh-1879qAA2fLYm/agent.22822'} Best regards, -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikmaru Honjo E-mail:honjo.rikimaru@ntt-tx.co.jp

3 3

Proposed Zuul UI changes for build summary page
by Sorin Sbarnea 16 Nov '20

16 Nov '20

As a result of the irc discussions from this week, I would like to propose some UI changes as described in the image below: https://sbarnea.com/ss/zuul-summary-ui-2020v2.png Each change has a letter so we can refer to them and implement them separately / gradually. zuul-cores are encouraged to reply and state if you support or disapprove any of these changes as this would avoid spending good amount of implementation and reviews. At least if any of the changes is problematic I can avoid working on it. When done we will have more space to display the "tabs", so less to scroll to see data, avoid hiding useful artifacts from the default UI by removing the extra click, overall a more compressed page, but not less readable. Please let me know what you think and how we can make it better. -- /sorin

5 6

Help with making a Zuul job wait for another job
by A richist 16 Nov '20

16 Nov '20

Hi everyone, I have what I feel like should be a basic use-case for Zuul, which I can't seem to get right. I have a project with 2 jobs set up as: *- job:* * name: job1* * run: <playbook> * * provides: build* * nodeset: nodeset1* *- job:* * name: job2* * run: <playbook> * * requires: build* * nodeset: nodeset2* *- project:* * check:* * jobs:* * - job1* * - job2* As you might have guessed, job1 builds the project and saves an artifact, while job2 requires that artifact and does something with it. I expected job1 to complete before job2 starts, however both jobs start simultaneously, which makes job2 unable to fulfill its purpose. I tried setting job2 to inherit job1: *- job:* * name: job1* * run: <playbook>* * nodeset: nodeset1* *- job:* * name: job2* * parent: job1* * post-run: <playbook> * * nodeset: nodeset2* *- project:* * check:* * jobs:* * - job2* However this seems to make job1's "run" playbook use "nodeset2", which is incompatible. job1 must run on nodeset1 and job2 must run on nodeset2. (Is there a way to make the "run" and "post-run" playbooks use different nodesets?) I might be missing something obvious here, would really appreciate your assistance. Regards, Arichist

2 2

AttributeError: 'Thread' object has no attribute 'isAlive' on Fedora 33 build VMs
by Jan Kundrát 13 Nov '20

13 Nov '20

Hi, I'm trying to add some Fedora 33 VMs to our setup with Zuul 3.18, however the very first job failed with this trace in the job log: [Zuul] Log Stream did not terminate w | MODULE FAILURE: w | <stdin>:18: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses w | Traceback (most recent call last): w | File "<stdin>", line 114, in <module> w | File "<stdin>", line 106, in _ansiballz_main w | File "<stdin>", line 49, in invoke_module w | File "/usr/lib64/python3.9/imp.py", line 234, in load_module w | return load_source(name, filename, file) w | File "/usr/lib64/python3.9/imp.py", line 169, in load_source w | module = _exec(spec, sys.modules[name]) w | File "<frozen importlib._bootstrap>", line 613, in _exec w | File "<frozen importlib._bootstrap_external>", line 790, in exec_module w | File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed w | File "/tmp/ansible_command_payload_zcmflb0m/__main__.py", line 675, in <module> w | File "/tmp/ansible_command_payload_zcmflb0m/__main__.py", line 651, in main w | File "/tmp/ansible_command_payload_zcmflb0m/__main__.py", line 498, in zuul_run_command w | AttributeError: 'Thread' object has no attribute 'isAlive' Older Fedoras work well. I think this code comes from Zuul, it is triggering a deprecated method in Python's threading which got removed in Python 3.9. I see that Zuul commit 758ba823f22366fe9da834612586b5f7c1829984 should probably fix it, but it is not included in any release. I can deploy from git just fine, but I'm sending it here as a suggestion to tag a release with a fix because this is not about the version of Python on the scheduler/executor, but on the VMs themselves. Or perhaps I'm wrong and it's code that origins in Ansible? With kind regards, Jan

3 3

zuul enqueue-ref issue with tenant value
by Åsmund Østvold 12 Nov '20

12 Nov '20

hi Again, Fantastic help I have received by this group! Still have some issues and I am wondering what I am doing wrong now. root@0374d1dcdc52:/# zuul enqueue-ref --tenant 192.168.167.126 --trigger gerrit --pipeline tag --project test/ensemble.service --ref refs/tags/v0.5.0-beta.7 --newrev 6b5efcf96a3ec713c991fc13b95f0d16385e85b8 Traceback (most recent call last): File "/usr/local/bin/zuul", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/site-packages/zuul/cmd/client.py", line 750, in main Client().main() File "/usr/local/lib/python3.8/site-packages/zuul/cmd/client.py", line 399, in main if self.args.func(): File "/usr/local/lib/python3.8/site-packages/zuul/cmd/client.py", line 526, in enqueue_ref r = client.enqueue_ref( File "/usr/local/lib/python3.8/site-packages/zuul/rpcclient.py", line 110, in enqueue_ref return not self.submitJob('zuul:enqueue_ref', data).failure File "/usr/local/lib/python3.8/site-packages/zuul/rpcclient.py", line 50, in submitJob raise RPCFailure(job.exception) zuul.rpcclient.RPCFailure: Invalid tenant: 192.168.167.126 Tenant config is like this: labels: - name: ubuntu-bionic providers: - name: static-vms driver: static pools: - name: main nodes: - name: 192.168.167.126 # stenant01 labels: ubuntu-bionic host-key-checking: False python-path: /usr/bin/python3 username: newton - name: 192.168.167.106 # stenant02 labels: ubuntu-bionic host-key-checking: False python-path: /usr/bin/python3 username: newton I am probably doing something wrong but what I do not know... If anybody see what I am doing wrong please let me know. Cheers, Åsmund

2 2

help reading logs
by Åsmund Østvold 10 Nov '20

10 Nov '20

hi I have an issue with a commit that will not trigger the jobs I expected. While investigating this I am trying to understand a log. The change I am trying to get in is e03b45eae13d35f65b6b111240d4638dea4fa9e2 it is on top of merge branch on project test/es. 2020-11-09 11:02:15,414 INFO zuul.Pipeline.resoptima.check_comment: Reporting enqueue, action [] item <QueueItem 0x7ff3203eed00 for <Change 0x7ff3204a6f10 test/es 2568,2> in check_comment> 2020-11-09 11:02:15,810 INFO zuul.MergeClient: [e: 92db9fd9a2e54c0dafcddb1959985c03] Merge <gear.Job 0x7ff3203ee310 handle: b'H:172.18.0.7:2123' name: merger:merge unique: d50b768a8e604d549647724bf939107a> complete, merged: True, updated: False, commit: e03b45eae13d35f65b6b111240d4638dea4fa9e2, branches: [] 2020-11-09 11:02:16,214 INFO zuul.MergeClient: [e: 92db9fd9a2e54c0dafcddb1959985c03] Merge <gear.Job 0x7ff3203ee7f0 handle: b'H:172.18.0.7:2124' name: merger:merge unique: 5ce30216a8aa41ecba7cbd653f62ddbf> complete, merged: True, updated: False, commit: e03b45eae13d35f65b6b111240d4638dea4fa9e2, branches: [] Nothing is logged to the gerrit change. Any hint on what is going one is of value Zuul version is: 3.19.1.dev390 f73434e4 Cheers, Åsmund

2 4

Zuul's test framework
by Matthieu Huin 05 Nov '20

05 Nov '20

Hello, Yesterday a discussion came up on IRC about using zuul's test framework in other projects [1]. Basically the framework greatly simplifies running zuul processes, and sets up projects and simulates a gerrit for testing. It is used for zuul, nodepool and zuul-client tests. The problem is that the framework lib is not available through a zuul import. That means that tests specific to nodepool, zuul-client and potentially other projects need to be defined within that framework, in the zuul project repo. This is not ideal, and in the case of zuul-client, it leads to tests being written in follow-up patches to the zuul repo, which is a bit backward [2]. Let's use this thread to suggest improvements on the situation, and weigh pros and cons. We could: 1. Copy the bootstrapping code to other projects that need it - this represents a significant amount of code, and it's going to be painful to ensure there are no divergences in the code base. 2. Split the test framework into its own package. You'll still need to invoke zuul's tox job to set it up, but at least the tests could live in their relevant project's repository. Any other alternatives? Cheers, [1] http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2020-09-28.log.html#… [2] see for example https://review.opendev.org/#/c/750709/ and testing in https://review.opendev.org/#/c/754103/ -- Matthieu Huin Senior Software Developer Red Hat <https://www.redhat.com> <https://red.ht/sig>

2 2

[Diversity] Diversity & Inclusion WG Meeting 11/2 - Removing Divisive Language
by Amy Marrich 30 Oct '20

30 Oct '20

The Diversity & Inclusion WG will continue working on the OSF's stance on the removal of Divisive Language within the OSF projects. We will be focusing on the creation of possible words to focus on as well as possible replacements[0] as was requested during our Forum session[1]. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, November 2nd, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. <https://meetpad.opendev.org/osf-diversity-and-inclusion> If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz) 0 - https://etherpad.opendev.org/p/wallaby-ptg-diversity 1- https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage

1 0