On Monday, December 5, 2016 11:47:59 AM CET Martin Juhl wrote: > Ok... Might have fixed that myself... > > Using the /centos/7.2.1511/cloud/x86_64/openstack-kilo/ it seems to work... > > Now i'm getting: > > ==> /var/log/copr-backend/vmm.log <== > [2016-12-05 11:15:37,384][ > INFO][vmm.event_handler][manager.py:add_vm_to_pool:175] registered new VM: > Copr builder 94671718 127.0.0.1 > [2016-12-05 11:18:37,256][ > INFO][vmm.event_handler][event_handle.py:on_health_check_result:112] check > fail threshold reached: 2, terminating: {u'vm_ip': u'127.0.0.1', u'vm_name': > u'Copr builder 760126240', u'topic': u'health_check', u'result': u'failed', > u'msg': u'VM is not responding to the testing playbook.Runner options: > {\'remote_user\': \'mockbuilder\', \'timeout\': 5, \'pattern\': \'127.0.0.1\', > \'forks\': 1, \'host_list\': \'127.0.0.1,\', \'transport\': > u\'paramiko\'}Ansible raw response:\n{\'dark\': {\'127.0.0.1\': {\'msg\': > "FAILED: (25, \'Inappropriate ioctl for device\')", \'failed\': True}}, > \'contacted\': {}}'} > [2016-12-05 11:18:37,257][ > INFO][vmm.event_handler][manager.py:start_vm_termination:283] VM Copr builder > 760126240 queued for termination > > Any ideas????
I usually try to run the playbook manually to spin up new VM and debug on lower level. Pavel _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org