Zuul ignores nodes with network_cli connections when running the setup playbook in order to support the use-case where a network appliance begins a job in an unreachable state. Starting with Zuul v4.6.0, for security reasons, host variables require a functioning Ansible connection in order to be set. This includes the Nodepool variables such as public and private IP addresses. Causing a network_cli host to become online after the start of a job requires this information, and so this functionality has not worked since 4.6.0. To correct this, we now always add in the nodepool host vars as originally set regardless of whether the variable freeze playbook runs for a particular host. This means that even if we have no other variables set for that host, we at least know the IP address of the host and can interact with it directly in order to bring it online. Additionally, the freeze playbook did not correctly check the return value, due to a typo. This accidentally allowed Zuul to continue to function in this situation (but without the nodepool variables accessible). With this change we continue to ignore the return value, but intentionally so. A test for this use-case is added, along with a releaso note. Change-Id: Icd8a2c035e6c04a7c198281adbd07fef422a6c63 Story: 2009226
Zuul
Zuul is a project gating system.
The latest documentation for Zuul v3 is published at: https://zuul-ci.org/docs/zuul/
If you are looking for the Edge routing service named Zuul that is related to Netflix, it can be found here: https://github.com/Netflix/zuul
If you are looking for the Javascript testing tool named Zuul, it can be found here: https://github.com/defunctzombie/zuul
Getting Help
There are two Zuul-related mailing lists:
- zuul-announce
-
A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.
- zuul-discuss
-
General discussion about Zuul, including questions about how to use it, and future development.
You will also find Zuul developers in the #zuul channel on Freenode IRC.
Contributing
To browse the latest code, see: https://opendev.org/zuul/zuul To clone the latest code, use git clone https://opendev.org/zuul/zuul
Bugs are handled at: https://storyboard.openstack.org/#!/project/zuul/zuul
Suspected security vulnerabilities are most appreciated if first reported privately following any of the supported mechanisms described at https://zuul-ci.org/docs/zuul/user/vulnerabilities.html
Code reviews are handled by gerrit at https://review.opendev.org
After creating a Gerrit account, use git review to submit patches. Example:
# Do your commits
$ git review
# Enter your username if prompted
Join #zuul on Freenode to discuss development or usage.
License
Zuul is free software. Most of Zuul is licensed under the Apache License, version 2.0. Some parts of Zuul are licensed under the General Public License, version 3.0. Please see the license headers at the tops of individual source files.
Python Version Support
Zuul requires Python 3. It does not support Python 2.
Since Zuul uses Ansible to drive CI jobs, Zuul can run tests anywhere Ansible can, including Python 2 environments.