Hi,
I see that this job ran 2 days ago. We indeed had a bug in our cleanup
which was fixed yesterday:
Can you try to re-trigger?
On Mon, Apr 2, 2018 at 9:58 AM, Barak Korren <bkorren(a)redhat.com> wrote:
Adding Dbelenky, infra.
On 2 April 2018 at 09:47, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> From [1], for example:
>
> 23:38:29 device-mapper: remove ioctl on
> docker-8:3-3221462509-a1a2c5a4ca437bb3760f453aebcf1f
12661009b511c5cb81ea088e5acd19b771
> failed: Device or resource busy
> 23:38:29 Command failed
> 23:38:29 Removing the used loop devices...
> 23:38:29 Redirecting to /bin/systemctl restart libvirtd.service
> 23:38:30 Stopping and removing all running containers
> 23:38:30 Traceback (most recent call last):
> 23:38:30 File
> "/home/jenkins/workspace/ovirt-system-tests_master_
check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py",
> line 468, in <module>
> 23:38:30 main()
> 23:38:30 File
> "/home/jenkins/workspace/ovirt-system-tests_master_
check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py",
> line 31, in main
> 23:38:30 stop_all_running_containers(client)
> 23:38:30 File
> "/home/jenkins/workspace/ovirt-system-tests_master_
check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py",
> line 120, in stop_all_running_containers
> 23:38:30 _get_container_name(container),
_get_container_id(container)
> 23:38:30 File
> "/home/jenkins/workspace/ovirt-system-tests_master_
check-patch-el7-x86_64/jenkins/scripts/docker_cleanup.py",
> line 128, in _get_container_name
> 23:38:30 return container['Labels']['name']
> 23:38:30 KeyError: 'name'
>
>
>
> Let me know if it's a known issue, or should I open a JIRA on it.
>
>
> Y.
> [1]
>
http://jenkins.ovirt.org/job/ovirt-system-tests_master_
check-patch-el7-x86_64/4806/console
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. |
redhat.com/trusted