[cinder][CI] Can't start zuul service
Hello every one, I'm building a CI system on my ubuntu 22 system. Now I've installed the zuul using 'pip install zuul' and configured it. But after running command 'zuul-scheduler', I saw a lot of errors like following in the log. It seems that there is something error in my config file that prevents access to the repo.
2024-09-20 13:05:06,010 ERROR zuul.TenantParser: Error processing cat job Traceback (most recent call last): File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2157, in _cacheTenantYAML self._processCatJob(abide, tenant, loading_errors, job, File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2249, in _processCatJob raise TimeoutError(f"Cat job {job} timed out; consider setting " TimeoutError: Cat job <zuul.zk.event_queues.JobResultFuture object at 0x7fb770341510> timed out; consider setting merger.git_timeout in zuul.conf
Following is my zuul.conf.
[zookeeper] hosts=ZOOKEEPER_HOST tls_cert=/cert/client-cert.pem tls_key=/cert/client-key.pem tls_ca=/cert/ca-cert.pem
[database] # Use variable interpolation to supply the password from the # docker-compose file. # https://zuul-ci.org/docs/zuul/latest/configuration.html dburi=mysql+pymysql://DB_USER:DB_PASS@DB_HOST/ZUUL_DB
[keystore] password=secret
[web] listen_address=0.0.0.0 port=9000 root=http://localhost:9000 log_config=/etc/zuul/logging.conf
[webclient] url=http://localhost:9000 verify_ssl=false
[scheduler] tenant_config=/etc/zuul/main.yaml log_config=/etc/zuul/logging.conf
[merger] git_user_email=git_user@example.com git_user_name=git_user log_config=/etc/zuul/logging.conf
[executor] private_key_file=/home/stack/.ssh/id_rsa default_username=executor_user trusted_rw_paths=/srv/static/logs
[connection gerrit] driver=gerrit server=review.opendev.org user=git_user sshkey=/ssh/id_rsa
And the following is the tenant_config file.
- tenant: name: myCI source: gerrit: untrusted-projects: - openstack/cinder
Could you please tell me what I need to modify or add in the config file? Thanks and Regards, Inori.
On Thu, Sep 19, 2024, at 11:35 PM, xuq.fnstxz@fujitsu.com wrote:
Hello every one, I'm building a CI system on my ubuntu 22 system.
Now I've installed the zuul using 'pip install zuul' and configured it. But after running command 'zuul-scheduler', I saw a lot of errors like following in the log. It seems that there is something error in my config file that prevents access to the repo.
2024-09-20 13:05:06,010 ERROR zuul.TenantParser: Error processing cat job Traceback (most recent call last): File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2157, in _cacheTenantYAML self._processCatJob(abide, tenant, loading_errors, job, File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2249, in _processCatJob raise TimeoutError(f"Cat job {job} timed out; consider setting " TimeoutError: Cat job <zuul.zk.event_queues.JobResultFuture object at 0x7fb770341510> timed out; consider setting merger.git_timeout in zuul.conf
The Zuul scheduler is asking the merger components to run cat jobs (these jobs `cat` the Zuul configs contained within in the git repos) and is not getting a response within the allocated timeout. This could be happening because the merger.git_timeout config option isn't set to a large enough value for your repos; opendev sets this value to 600 seconds [0] which may be necessary for larger repos like Nova. Another reason this could be happening is you have no merger components running. The zuul-merger and zuul-executor services both run merger components. You will also need a zuul-executor running to execute jobs. Do you have a zuul-executor service running as part of this cluster? If you do not, I would start by adding one. If you do, then you should see the merge requests getting processed in the logs there which may offer further clues to why this is happening. If you haven't run through it yet, the Zuul quickstart tutorial [1] is a good walkthrough of the various components and how to get things working. I wouldn't use the quickstart environment in production without some modification because it doesn't use a secure zookeeper db encryption password nor does it offer TLS for the API/Web service. However, it can be used as a starting point and modified to do so. Finally, the Zuul community can be reached on Matrix in the #zuul:opendev.org room [2] and via the zuul-discuss mailing list [3]. You might find Zuul debugging help is more readily available there than on the openstack list. [0] https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/... [1] https://zuul-ci.org/docs/zuul/latest/tutorials/quick-start.html [2] https://matrix.to/#/#zuul:opendev.org [3] https://lists.zuul-ci.org/mailman3/lists/zuul-discuss.lists.zuul-ci.org/
Clark Boylan wrote:
On Thu, Sep 19, 2024, at 11:35 PM, xuq.fnstxz@fujitsu.com wrote:
Hello every one, I'm building a CI system on my ubuntu 22 system. Now I've installed the zuul using 'pip install zuul' and configured it. But after running command 'zuul-scheduler', I saw a lot of errors like following in the log. It seems that there is something error in my config file that prevents access to the repo. 2024-09-20 13:05:06,010 ERROR zuul.TenantParser: Error processing cat job Traceback (most recent call last): File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2157, in _cacheTenantYAML self._processCatJob(abide, tenant, loading_errors, job, File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2249, in _processCatJob raise TimeoutError(f"Cat job {job} timed out; consider setting " TimeoutError: Cat job <zuul.zk.event_queues.JobResultFuture object at 0x7fb770341510> timed out; consider setting merger.git_timeout in zuul.conf The Zuul scheduler is asking the merger components to run cat jobs (these jobs `cat` the Zuul configs contained within in the git repos) and is not getting a response within the allocated timeout. This could be happening because the merger.git_timeout config option isn't set to a large enough value for your repos; opendev sets this value to 600 seconds [0] which may be necessary for larger repos like Nova. Another reason this could be happening is you have no merger components running. The zuul-merger and zuul-executor services both run merger components. You will also need a zuul-executor running to execute jobs. Do you have a zuul-executor service running as part of this cluster? If you do not, I would start by adding one. If you do, then you should see the merge requests getting processed in the logs there which may offer further clues to why this is happening. If you haven't run through it yet, the Zuul quickstart tutorial [1] is a good walkthrough of the various components and how to get things working. I wouldn't use the quickstart environment in production without some modification because it doesn't use a secure zookeeper db encryption password nor does it offer TLS for the API/Web service. However, it can be used as a starting point and modified to do so. Finally, the Zuul community can be reached on Matrix in the #zuul:opendev.org room [2] and via the zuul-discuss mailing list [3]. You might find Zuul debugging help is more readily available there than on the openstack list. [0] https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/... [1] https://zuul-ci.org/docs/zuul/latest/tutorials/quick-start.html [2] https://matrix.to/#/#zuul:opendev.org [3] https://lists.zuul-ci.org/mailman3/lists/zuul-discuss.lists.zuul-ci.org/
Hi Clark, Thank you so much for your response to my question. I will try your suggestions mentioned in your mail. If those don't work, I'll reach out to the zuul-discuss mailing list for further assistance. Thanks again for your time and help! Thanks and Regards, Inori.
participants (2)
-
Clark Boylan
-
xuq.fnstxz＠fujitsu.com