Comment 2 for bug 1663464

Yes this is reproducible (I am seeing it each time while provisioning) and there wasn't any network issue. Seen on 3039 too -

2017-02-14 02:00:58:661673: [root@10.204.216.232] out: [localhost] local: chkconfig nova-compute on
2017-02-14 02:00:58:661934: [root@10.204.216.232] out: [localhost] local: service nova-compute restart
2017-02-14 02:00:58:662075: [root@10.204.216.232] out: nova-compute stop/waiting
2017-02-14 02:00:58:694211: [root@10.204.216.232] out: nova-compute start/running, process 27934
2017-02-14 02:00:58:726012: [root@10.204.216.232] out: [localhost] local: chkconfig supervisor-vrouter on
2017-02-14 02:00:58:726164: [root@10.204.216.232] out:
2017-02-14 02:00:58:757877:
2017-02-14 02:00:58:758489: No env.dpdk section in testbed file, skipping the configuration...
2017-02-14 02:00:58:758699: [root@10.204.216.232] Executing task 'prov_config'
2017-02-14 02:00:58:759079: [root@10.204.216.232] sudo: hostname
2017-02-14 02:00:58:759447: [root@10.204.216.232] out: nodek12
2017-02-14 02:00:58:809587: [root@10.204.216.232] out:
2017-02-14 02:00:58:809964: Write failed: Broken pipe
+ rv=255
+ return 255
+ debug_and_die 'fab setup_interface or setup_all task failed'
+ local 'message=fab setup_interface or setup_all task failed'