Interesting - just added the shrink script a few days ago, and this didn't happen to me in testing the latest versions of 10.7-10.10. Presumably, removing just the call to vmware-tools-cli would be a sufficient workaround: However, I have checked that removing shrink.sh from the list of scripts in the template.json does allow the build to run to completion. I haven't yet checked whether the user closing this pop-up in time will save the build. I think that it may have been because this pop-up was not closed that the VM could not be shutdown gracefully. I didn't click "OK" (when I had the chance). (The build log obviously says that such warnings should be disregarded). While the shrink process was running, I noticed that, there was a pop-up box in the guest VM with a warning that there is no disk space left.
=> Builds finished but no artifacts were created. > vmware-iso: Failed to send shutdown command: dial tcp 172.16.96.142:22: i/o timeout => Some builds didn't complete successfully and had errors: => vmware-iso: Deleting output directory.īuild 'vmware-iso' errored: Failed to send shutdown command: dial tcp 172.16.96.142:22: i/o timeout
=> vmware-iso: Failed to send shutdown command: dial tcp 172.16.96.142:22: i/o timeout => vmware-iso: Gracefully halting virtual machine. Vmware-iso: Please disregard any warnings about disk space for the duration of shrink process. vmware-iso: Provisioning with shell script.
0 kommentar(er)
