search

Cimpress-MCP / vagrant-orchestrate

Cross platform deployment orchestration to existing managed servers using vagrant provisioners
Other
19 stars 13 forks source link

Deployments fail in v0.8.0 if certain folders do not exist, or are not readable #47

Open theopak opened 8 years ago

theopak commented 8 years ago

Using v0.8.0 I run into deployment errors related to the existence of folders. I can avert the issue by SSHing into the target boxes and making sure the specified folders exist / don't exist as necessary, but that's tedious. @chrisbaldauf mentioned that this is the probable root cause: Possible root cause: https://github.com/Cimpress-MCP/vagrant-orchestrate/blob/master/lib/vagrant-managed-servers/action/take_synced_folder_ownership.rb#L39

The fix for now is to use a different version of the plugin:

$ vagrant plugin uninstall vagrant-orchestrate
Uninstalling the 'vagrant-orchestrate' plugin...
$ vagrant plugin install vagrant-orchestrate --plugin-version 0.7.2
Installing the 'vagrant-orchestrate --version '0.7.2'' plugin. This can take a few minutes...
Installed the plugin 'vagrant-orchestrate (0.7.2)'!

Error message:

$ vagrant orchestrate push
…

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown 'ice' -R /tmp/.gokeys

Stdout from the command:

Stderr from the command:

stdin: is not a tty
chown: cannot access ‘/tmp/.gokeys’: No such file or directory
chrisbaldauf commented 8 years ago

@theopak, thanks for the report. I think I see what is going on and should be able to get a fix out tomorrow. If anyone else runs into this issue, there are two available workarounds:

  1. Revert to 0.7.2 as @theopak detailed above
  2. Set config.orchestrate.take_synced_folder_ownership = false in your Vagrantfile.

https://github.com/Cimpress-MCP/vagrant-orchestrate/blob/master/docs/config.md#take_synced_folder_ownership