On Wed, Oct 04, 2017 at 02:39:17PM +0900, Rikimaru Honjo wrote: > Hello, > > I'm trying to run jobs with Zuul v3 in my local environment.[1] > I prepared a sample job that runs sleep command on zuul's host. > This job doesn't use Nodepool. [2] > > As a result, Zuul v3 submitted "SUCCESS" to gerrit when gerrit event occurred. > But, error logs were generated. And my job was not run. > > I'd appreciate it if you help me. > (Should I write this topic on Zuul Storyboard?) > > [1]I use Ubuntu 16.04 and zuul==2.5.3.dev1374. > > [2]In my understanding, I can use Zuul v3 without Nodepool. > https://docs.openstack.org/infra/zuul/feature/zuulv3/user/config.html#attr-job.nodeset > > If a job has an empty or no nodeset definition, it will still run and may > > be able to perform actions on the Zuul executor. > While this is true, at this time it has limited testing and not sure I would be writing job content to leverage this too much. Right now, we are only using it to trigger RTFD hooks in openstack-infra.
Zuulv3 is really meant to be used with nodepool, much tighter now then before. We do have plan to support static nodes in zuulv3, but work on that hasn't finished. > [Conditions] > * Target project is defined as config-project in tenant configuration file. > * I didn't write nodeset in .zuul.yaml. > Because my job doesn't use Nodepool. > * I configured playbooks's hosts as "- hosts: all" or "- hosts: localhost". > (I referred to project-config repository.) > > [Error logs] > "no hosts matched" or "list index out of range" were generated. > Please see the attached file. > > > On 2017/09/29 23:58, Monty Taylor wrote: > > Hey everybody! > > > > tl;dr - If you're having issues with your jobs, check the FAQ, this email > > and followups on this thread for mentions of them. If it's an issue with > > your job and you can spot it (bad config) just submit a patch with topic > > 'zuulv3'. If it's bigger/weirder/you don't know - we'd like to ask that you > > send a follow up email to this thread so that we can ensure we've got them > > all and so that others can see it too. > > > > ** Zuul v3 Migration Status ** > > > > If you haven't noticed the Zuul v3 migration - awesome, that means it's > > working perfectly for you. > > > > If you have - sorry for the disruption. It turns out we have a REALLY > > complicated array of job content you've all created. Hopefully the pain of > > the moment will be offset by the ability for you to all take direct > > ownership of your awesome content... so bear with us, your patience is > > appreciated. > > > > If you find yourself with some extra time on your hands while you wait on > > something, you may find it helpful to read: > > > > https://docs.openstack.org/infra/manual/zuulv3.html > > > > We're adding content to it as issues arise. Unfortunately, one of the > > issues is that the infra manual publication job stopped working. > > > > While the infra manual publication is being fixed, we're collecting FAQ > > content for it in an etherpad: > > > > https://etherpad.openstack.org/p/zuulv3-migration-faq > > > > If you have a job issue, check it first to see if we've got an entry for > > it. Once manual publication is fixed, we'll update the etherpad to point to > > the FAQ section of the manual. > > > > ** Global Issues ** > > > > There are a number of outstanding issues that are being worked. As of right > > now, there are a few major/systemic ones that we're looking in to that are > > worth noting: > > > > * Zuul Stalls > > > > If you say to yourself "zuul doesn't seem to be doing anything, did I do > > something wrong?", we're having an issue that jeblair and Shrews are > > currently tracking down with intermittent connection issues in the backend > > plumbing. > > > > When it happens it's an across the board issue, so fixing it is our number > > one priority. > > > > * Incorrect node type > > > > We've got reports of things running on trusty that should be running on > > xenial. The job definitions look correct, so this is also under > > investigation. > > > > * Multinode jobs having POST FAILURE > > > > There is a bug in the log collection trying to collect from all nodes while > > the old jobs were designed to only collect from the 'primary'. Patches are > > up to fix this and should be fixed soon. > > > > * Branch Exclusions being ignored > > > > This has been reported and its cause is currently unknown. > > > > Thank you all again for your patience! This is a giant rollout with a bunch > > of changes in it, so we really do appreciate everyone's understanding as we > > work through it all. > > > > Monty > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > -- > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > Rikimaru Honjo > E-mail:honjo.rikim...@po.ntt-tx.co.jp > > > Case1)I configures playbooks's hosts as "- hosts: all". > > 2017-09-29 16:18:40,247 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Writing logging config for job > /tmp/e56656cd5d1444619c01755e6f858be0/work/logs/job-output.txt > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/logging.json > 2017-09-29 16:18:40,249 DEBUG zuul.BubblewrapExecutionContext: Bubblewrap > command: bwrap --dir /tmp --tmpfs /tmp --dir /var --dir /var/tmp --dir > /run/user/1000 --ro-bind /usr /usr --ro-bind /lib /lib --ro-bind /bin /bin > --ro-bind /sbin /sbin --ro-bind /etc/resolv.conf /etc/resolv.conf --ro-bind > /etc/hosts /etc/hosts --ro-bind /tmp/ssh-WDBthw8Kiv3s/agent.8420 > /tmp/ssh-WDBthw8Kiv3s/agent.8420 --bind > /tmp/e56656cd5d1444619c01755e6f858be0/work > /tmp/e56656cd5d1444619c01755e6f858be0/work --proc /proc --dev /dev --chdir > /tmp/e56656cd5d1444619c01755e6f858be0/work --unshare-all --share-net --uid > 1000 --gid 1000 --file 14 /etc/passwd --file 16 /etc/group --ro-bind /lib64 > /lib64 --ro-bind /etc/nsswitch.conf /etc/nsswitch.conf --ro-bind > /etc/alternatives /etc/alternatives --ro-bind /var/lib/zuul/ansible > /var/lib/zuul/ansible --ro-bind /tmp/e56656cd5d1444619c01755e6f858be0/ansible > /tmp/e56656cd5d1444619c01755e6f858be0/ansible --ro-bind > /tmp/e56656cd5d1444619c01755e6f858be0/trusted > /tmp/e56656cd5d1444619c01755e6f858be0/trusted --ro-bind > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/setup_playbook > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/setup_playbook --bind > /tmp/e56656cd5d1444619c01755e6f858be0/.ansible > /tmp/e56656cd5d1444619c01755e6f858be0/.ansible > 2017-09-29 16:18:40,249 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible command: > ANSIBLE_CONFIG=/tmp/e56656cd5d1444619c01755e6f858be0/ansible/setup_playbook/ansible.cfg > ansible '*' -v -m setup -a 'gather_subset=!all' > 2017-09-29 16:18:40,823 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b'Using > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/setup_playbook/ansible.cfg as > config file' > 2017-09-29 16:18:40,841 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b' [WARNING]: provided > hosts list is empty, only localhost is available' > 2017-09-29 16:18:40,842 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b' [WARNING]: No hosts > matched, nothing to do' > 2017-09-29 16:18:41,101 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output terminated > 2017-09-29 16:18:41,102 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible exit code: 0 > 2017-09-29 16:18:41,102 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Stopped watchdog > 2017-09-29 16:18:41,102 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Stopped disk job killer > 2017-09-29 16:18:41,102 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible complete, result RESULT_NORMAL code > 0 > 2017-09-29 16:18:41,103 DEBUG zuul.BubblewrapExecutionContext: Bubblewrap > command: bwrap --dir /tmp --tmpfs /tmp --dir /var --dir /var/tmp --dir > /run/user/1000 --ro-bind /usr /usr --ro-bind /lib /lib --ro-bind /bin /bin > --ro-bind /sbin /sbin --ro-bind /etc/resolv.conf /etc/resolv.conf --ro-bind > /etc/hosts /etc/hosts --ro-bind /tmp/ssh-WDBthw8Kiv3s/agent.8420 > /tmp/ssh-WDBthw8Kiv3s/agent.8420 --bind > /tmp/e56656cd5d1444619c01755e6f858be0/work > /tmp/e56656cd5d1444619c01755e6f858be0/work --proc /proc --dev /dev --chdir > /tmp/e56656cd5d1444619c01755e6f858be0/work --unshare-all --share-net --uid > 1000 --gid 1000 --file 15 /etc/passwd --file 16 /etc/group --ro-bind /lib64 > /lib64 --ro-bind /etc/nsswitch.conf /etc/nsswitch.conf --ro-bind > /etc/alternatives /etc/alternatives --ro-bind /var/lib/zuul/ansible > /var/lib/zuul/ansible --ro-bind /tmp/e56656cd5d1444619c01755e6f858be0/ansible > /tmp/e56656cd5d1444619c01755e6f858be0/ansible --ro-bind > /tmp/e56656cd5d1444619c01755e6f858be0/trusted > /tmp/e56656cd5d1444619c01755e6f858be0/trusted --ro-bind > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/playbook_0 > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/playbook_0 --bind > /tmp/e56656cd5d1444619c01755e6f858be0/.ansible > /tmp/e56656cd5d1444619c01755e6f858be0/.ansible > 2017-09-29 16:18:41,103 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible command: > ANSIBLE_CONFIG=/tmp/e56656cd5d1444619c01755e6f858be0/ansible/playbook_0/ansible.cfg > ansible-playbook -v > /tmp/e56656cd5d1444619c01755e6f858be0/trusted/project_0/192.168.10.126/masakari-project/playbooks/masakari-project.yaml > -e zuul_execution_phase=run -e zuul_execution_trusted=True -e > zuul_execution_canonical_name_and_path=192.168.10.126/masakari-project/playbooks/masakari-project > -e zuul_execution_branch=master > 2017-09-29 16:18:41,744 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b'Using > /tmp/e56656cd5d1444619c01755e6f858be0/ansible/playbook_0/ansible.cfg as > config file' > 2017-09-29 16:18:41,762 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b' [WARNING]: provided > hosts list is empty, only localhost is available' > 2017-09-29 16:18:41,946 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b' [WARNING]: Failure using > method (v2_playbook_on_play_start) in callback plugin' > 2017-09-29 16:18:41,947 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: > b"(<ansible.plugins.callback.zuul_stream.CallbackModule object at > 0x7f34a1a2e470>): 'NoneType' object has no attribute" > 2017-09-29 16:18:41,947 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b"'values'" > 2017-09-29 16:18:41,947 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b' [WARNING]: Failure using > method (v2_playbook_on_play_start) in callback plugin' > 2017-09-29 16:18:41,947 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: > b'(<ansible.plugins.callback./var/lib/zuul/ansible/zuul/ansible/callback/zuul_json.CallbackModule > object at' > 2017-09-29 16:18:41,947 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b"0x7f34a1047ba8>): > 'NoneType' object has no attribute 'values'" > 2017-09-29 16:18:41,948 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output: b'skipping: no hosts > matched' > 2017-09-29 16:18:41,998 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible output terminated > 2017-09-29 16:18:41,999 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible exit code: 0 > 2017-09-29 16:18:41,999 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Stopped disk job killer > 2017-09-29 16:18:41,999 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Ansible complete, result RESULT_NORMAL code > 0 > 2017-09-29 16:18:42,000 DEBUG zuul.AnsibleJob: [build: > e56656cd5d1444619c01755e6f858be0] Sending result: {"result": "SUCCESS", > "data": {}} > > Case2)I configures playbooks's hosts as "- hosts: localhost". > > 2017-10-02 15:39:00,968 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Writing logging config for job > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work/logs/job-output.txt > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/logging.json > 2017-10-02 15:39:00,971 DEBUG zuul.BubblewrapExecutionContext: Bubblewrap > command: bwrap --dir /tmp --tmpfs /tmp --dir /var --dir /var/tmp --dir > /run/user/1000 --ro-bind /usr /usr --ro-bind /lib /lib --ro-bind /bin /bin > --ro-bind /sbin /sbin --ro-bind /etc/resolv.conf /etc/resolv.conf --ro-bind > /etc/hosts /etc/hosts --ro-bind /tmp/ssh-C8amU70LglpG/agent.14749 > /tmp/ssh-C8amU70LglpG/agent.14749 --bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work --proc /proc --dev /dev --chdir > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work --unshare-all --share-net --uid > 1000 --gid 1000 --file 14 /etc/passwd --file 15 /etc/group --ro-bind /lib64 > /lib64 --ro-bind /etc/nsswitch.conf /etc/nsswitch.conf --ro-bind > /etc/alternatives /etc/alternatives --ro-bind /var/lib/zuul/ansible > /var/lib/zuul/ansible --ro-bind /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible --ro-bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/trusted > /tmp/cd75e24c10f849c6929f47d866b5d8d4/trusted --ro-bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/setup_playbook > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/setup_playbook --bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/.ansible > /tmp/cd75e24c10f849c6929f47d866b5d8d4/.ansible > 2017-10-02 15:39:00,973 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible command: > ANSIBLE_CONFIG=/tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/setup_playbook/ansible.cfg > ansible '*' -v -m setup -a 'gather_subset=!all' > 2017-10-02 15:39:01,693 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b'Using > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/setup_playbook/ansible.cfg as > config file' > 2017-10-02 15:39:01,713 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: provided > hosts list is empty, only localhost is available' > 2017-10-02 15:39:01,714 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: No hosts > matched, nothing to do' > 2017-10-02 15:39:01,991 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output terminated > 2017-10-02 15:39:01,992 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible exit code: 0 > 2017-10-02 15:39:01,992 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Stopped watchdog > 2017-10-02 15:39:01,992 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Stopped disk job killer > 2017-10-02 15:39:01,992 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible complete, result RESULT_NORMAL code > 0 > 2017-10-02 15:39:01,993 DEBUG zuul.BubblewrapExecutionContext: Bubblewrap > command: bwrap --dir /tmp --tmpfs /tmp --dir /var --dir /var/tmp --dir > /run/user/1000 --ro-bind /usr /usr --ro-bind /lib /lib --ro-bind /bin /bin > --ro-bind /sbin /sbin --ro-bind /etc/resolv.conf /etc/resolv.conf --ro-bind > /etc/hosts /etc/hosts --ro-bind /tmp/ssh-C8amU70LglpG/agent.14749 > /tmp/ssh-C8amU70LglpG/agent.14749 --bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work --proc /proc --dev /dev --chdir > /tmp/cd75e24c10f849c6929f47d866b5d8d4/work --unshare-all --share-net --uid > 1000 --gid 1000 --file 15 /etc/passwd --file 16 /etc/group --ro-bind /lib64 > /lib64 --ro-bind /etc/nsswitch.conf /etc/nsswitch.conf --ro-bind > /etc/alternatives /etc/alternatives --ro-bind /var/lib/zuul/ansible > /var/lib/zuul/ansible --ro-bind /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible --ro-bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/trusted > /tmp/cd75e24c10f849c6929f47d866b5d8d4/trusted --ro-bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/playbook_0 > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/playbook_0 --bind > /tmp/cd75e24c10f849c6929f47d866b5d8d4/.ansible > /tmp/cd75e24c10f849c6929f47d866b5d8d4/.ansible > 2017-10-02 15:39:01,994 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible command: > ANSIBLE_CONFIG=/tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/playbook_0/ansible.cfg > ansible-playbook -v > /tmp/cd75e24c10f849c6929f47d866b5d8d4/trusted/project_0/192.168.10.126/masakari-project/playbooks/masakari-project.yaml > -e zuul_execution_phase=run -e zuul_execution_trusted=True -e > zuul_execution_canonical_name_and_path=192.168.10.126/masakari-project/playbooks/masakari-project > -e zuul_execution_branch=master > 2017-10-02 15:39:02,629 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b'Using > /tmp/cd75e24c10f849c6929f47d866b5d8d4/ansible/playbook_0/ansible.cfg as > config file' > 2017-10-02 15:39:02,646 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: provided > hosts list is empty, only localhost is available' > 2017-10-02 15:39:02,828 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: Failure using > method (v2_playbook_on_play_start) in callback plugin' > 2017-10-02 15:39:02,829 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: > b'(<ansible.plugins.callback.zuul_stream.CallbackModule object at > 0x7f14cb7c67b8>):' > 2017-10-02 15:39:02,829 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: Failure using > method (v2_playbook_on_play_start) in callback plugin' > 2017-10-02 15:39:02,829 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: > b'(<ansible.plugins.callback./var/lib/zuul/ansible/zuul/ansible/callback/zuul_json.CallbackModule > object at' > 2017-10-02 15:39:02,829 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b'0x7f14caddcba8>):' > 2017-10-02 15:39:02,853 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: Failure using > method (v2_playbook_on_task_start) in callback plugin' > 2017-10-02 15:39:02,854 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: > b'(<ansible.plugins.callback./var/lib/zuul/ansible/zuul/ansible/callback/zuul_json.CallbackModule > object at' > 2017-10-02 15:39:02,854 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b'0x7f14caddcba8>): list > index out of range' > 2017-10-02 15:39:03,402 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b' [WARNING]: Failure using > method (v2_runner_on_ok) in callback plugin' > 2017-10-02 15:39:03,402 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: > b'(<ansible.plugins.callback./var/lib/zuul/ansible/zuul/ansible/callback/zuul_json.CallbackModule > object at' > 2017-10-02 15:39:03,402 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output: b'0x7f14caddcba8>): list > index out of range' > 2017-10-02 15:39:03,987 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible output terminated > 2017-10-02 15:39:03,987 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible exit code: 0 > 2017-10-02 15:39:03,987 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Stopped disk job killer > 2017-10-02 15:39:03,988 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Ansible complete, result RESULT_NORMAL code > 0 > 2017-10-02 15:39:03,988 DEBUG zuul.AnsibleJob: [build: > cd75e24c10f849c6929f47d866b5d8d4] Sending result: {"result": "SUCCESS", > "data": {"zuul": {"log_url": "http://192.168.10.22:8000/"}}} > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
