由于错误 "File already exists"，使用 CodeDeploy 的部署在 "install" 步失败
Deployment using CodeDeploy failing at "install" step due to error "File already exists"
这是我在 "install" 步骤遇到的错误 -
File already exists at location /var/cake_1.2.0.6311-beta/app/webroot/../../somefile.php
我无法断定是什么事件导致了这种情况。但我记得的是这个 -
我通过 jenkins 启动了部署（集成了代码部署插件）。部署在 "install" 步失败，出现我在上面粘贴的错误。
注意 - 这是 appspec.yml 文件的文件部分中的第一个文件。
据我所知，我在同一个部署组上做了一些部署，直接通过代码部署（很可能使用 Jenkins 在上述步骤中创建的相同 S3 文件）并且成功了.
- 然后我有几次失败的部署（故意在不同的步骤失败，例如 beforeInstall 以非零数字退出）。
此后，即使直接通过代码部署，我也无法成功部署。
背景
我检查了 this question which appears related and tried by deleting everything inside /opt/codedeploy-agent/deployment-root/, as in mentioned in one of the answers，但是，它导致在我的实例中部署的代码损坏，并且通过 Jenkins 部署开始抛出此错误，指出来自存档的 appspec 文件（它试图寻找上次成功的部署，它似乎，已被删除）未找到 -
然后我在实例上重新安装了代码部署，上面提到的步骤就是我之后所做的。
更新 - 打开赏金
正如 Rodrigo M 的回答，到目前为止，从实例上的部署路径中删除此类文件对我来说一直有效，但对于这个特定文件来说同样无效 -
File already exists at location /var/cake_1.2.0.6311-beta/deployment/serverLoad.json
我验证了以下内容 -
在所有实例上从上述位置删除文件后，我进行了新的部署。我观察到文件重新出现了，但仍然抛出与上述相同的错误并且部署失败。
在不删除的情况下，我将文件更改为 777。结果相同。
有趣的是，昨天我收到了多个文件的错误，当我找到它们并进行新构建时，我将它们一个一个删除。除了这个文件外，所有其他文件的问题都得到了解决，即使删除也不起作用。我不知道！
注意 - 我现在所做的所有部署都是由 Jenkins 触发的（没有从 AWS 代码部署触发的直接部署）。
这是来自 /var/log/aws/codedeploy-agent/codedeploy-agent.log 的日志记录，其中包含相关的错误堆栈跟踪 -
2016-11-10 07:38:12 INFO [codedeploy-agent(16889)]: Version file found in /opt/codedeploy-agent/.version.
2016-11-10 07:38:12 INFO [codedeploy-agent(16889)]: [Aws::CodeDeployCommand::Client 200 0.025545 0 retries] put_host_command_complete(command_status:"Failed",diagnostics:{format:"JSON",payload:"{\"error_code\":5,\"script_name\":\"\",\"message\":\"File already exists at location /var/cake_1.2.0.6311-beta/deployment/serverLoad.json\",\"log\":\"\"}"},host_command_identifier:"WyJjb20uYW1hem9uLmFwb2xsby5kZXBsb3ljb250cm9sLmRvbWFpbi5Ib3N0Q29tbWFuZElkZW50aWZpZXIiLHsiZGVwbG95bWVudElkIjoiQ29kZURlcGxveS91cy1lYXN0LTEvUHJvZC9hcm46YXdzOnNkczp1cy1lYXN0LTE6Mzc3NzAzOTYxOTk4OmRlcGxveW1lbnQvZC1VOVFPR0RBWUkiLCJob3N0SWQiOiJhcm46YXdzOmVjMjp1cy1lYXN0LTE6Mzc3NzAzOTYxOTk4Omluc3RhbmNlL2ktZWNmYzU1YTkiLCJjb21tYW5kTmFtZSI6Ikluc3RhbGwiLCJjb21tYW5kUG9zaXRpb24iOjQsImNvbW1hbmRBdHRlbXB0IjoxfV0=")
2016-11-10 07:38:12 ERROR [codedeploy-agent(16889)]: InstanceAgent::Plugins::CodeDeployPlugin::CommandPoller: Error during perform: RuntimeError - File already exists at location /var/cake_1.2.0.6311-beta/deployment/serverLoad.json - /opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:115:in `generate_normal_copy'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:67:in `block (2 levels) in generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:55:in `each'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:55:in `block in generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/install_instruction.rb:68:in `generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:54:in `generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:34:in `install'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_executor.rb:114:in `block in <class:CommandExecutor>'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_executor.rb:62:in `execute_command'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_poller.rb:132:in `process_command'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_poller.rb:65:in `perform'
/opt/codedeploy-agent/lib/instance_agent/agent/base.rb:28:in `run'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:38:in `block in run'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:55:in `with_error_handling'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:37:in `run'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:70:in `block in run_with_error_handling'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:55:in `with_error_handling'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:69:in `run_with_error_handling'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:33:in `block in start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:22:in `loop'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:22:in `start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:206:in `block in spawn_child'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:204:in `fork'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:204:in `spawn_child'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:196:in `block in spawn_children'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:195:in `times'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:195:in `spawn_children'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:134:in `start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:37:in `block in start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:36:in `fork'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:36:in `start'
/opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:41:in `block (2 levels) in <main>'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/command_support.rb:130:in `call'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/command_support.rb:130:in `execute'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:262:in `block in call_command'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:275:in `call'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:275:in `call_command'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:69:in `run'
/opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:88:in `<main>'
更新 2
我能够通过重命名 json 文件并删除 appspec.yml 中的旧文件引用来应用脏修复。但是，在新的部署组（带有新的 ec2 实例）上，新的 json 文件导致相同的文件退出问题。每次改文件名都很痛苦。对正在发生的事情感到非常恼火。
作为其流程的一部分，CodeDeploy 将查找有关 app/deployment 组先前部署文件的信息。 If then it uses this info to delete existing files, preparing for deployment for new revisions, as needed.
http://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-steps.html#deployment-rollback
在这种情况下，由于您之前可能进行了手动清理，因此存在一些不一致的引用。
对于所有部署来说，一个不错的选择是在 BeforeInstall 挂钩期间简单地删除部署文件夹中的所有文件。这将解决现在和以后的问题。
这是可以解决的。 Codedeploy 对其自身未部署的文件抛出错误。但是有一个选项可以在部署期间覆盖它。
"内容选项：
当目标实例上的文件与应用程序修订中的文件同名且目标位置相同时，选择 AWS CodeDeploy 在部署期间采取的操作。"
您可以选择失败、覆盖和保留。这取决于你的情况。
您可以找到更多信息
docs.aws.amazon.com（奇怪在'rollback'下）
cli docs.aws.amazon.com（参见 --file-exists-behavior（字符串））
这是我在 "install" 步骤遇到的错误 -
File already exists at location /var/cake_1.2.0.6311-beta/app/webroot/../../somefile.php
我无法断定是什么事件导致了这种情况。但我记得的是这个 -
我通过 jenkins 启动了部署（集成了代码部署插件）。部署在 "install" 步失败，出现我在上面粘贴的错误。
注意 - 这是 appspec.yml 文件的文件部分中的第一个文件。
据我所知，我在同一个部署组上做了一些部署，直接通过代码部署（很可能使用 Jenkins 在上述步骤中创建的相同 S3 文件）并且成功了.
- 然后我有几次失败的部署（故意在不同的步骤失败，例如 beforeInstall 以非零数字退出）。
此后，即使直接通过代码部署，我也无法成功部署。
背景
我检查了 this question which appears related and tried by deleting everything inside /opt/codedeploy-agent/deployment-root/, as in mentioned in one of the answers，但是，它导致在我的实例中部署的代码损坏，并且通过 Jenkins 部署开始抛出此错误，指出来自存档的 appspec 文件（它试图寻找上次成功的部署，它似乎，已被删除）未找到 -
然后我在实例上重新安装了代码部署，上面提到的步骤就是我之后所做的。
更新 - 打开赏金
正如 Rodrigo M 的回答，到目前为止，从实例上的部署路径中删除此类文件对我来说一直有效，但对于这个特定文件来说同样无效 -
File already exists at location /var/cake_1.2.0.6311-beta/deployment/serverLoad.json
我验证了以下内容 -
在所有实例上从上述位置删除文件后，我进行了新的部署。我观察到文件重新出现了，但仍然抛出与上述相同的错误并且部署失败。
在不删除的情况下，我将文件更改为 777。结果相同。
有趣的是，昨天我收到了多个文件的错误，当我找到它们并进行新构建时，我将它们一个一个删除。除了这个文件外，所有其他文件的问题都得到了解决，即使删除也不起作用。我不知道！
注意 - 我现在所做的所有部署都是由 Jenkins 触发的（没有从 AWS 代码部署触发的直接部署）。
这是来自 /var/log/aws/codedeploy-agent/codedeploy-agent.log 的日志记录，其中包含相关的错误堆栈跟踪 -
2016-11-10 07:38:12 INFO [codedeploy-agent(16889)]: Version file found in /opt/codedeploy-agent/.version.
2016-11-10 07:38:12 INFO [codedeploy-agent(16889)]: [Aws::CodeDeployCommand::Client 200 0.025545 0 retries] put_host_command_complete(command_status:"Failed",diagnostics:{format:"JSON",payload:"{\"error_code\":5,\"script_name\":\"\",\"message\":\"File already exists at location /var/cake_1.2.0.6311-beta/deployment/serverLoad.json\",\"log\":\"\"}"},host_command_identifier:"WyJjb20uYW1hem9uLmFwb2xsby5kZXBsb3ljb250cm9sLmRvbWFpbi5Ib3N0Q29tbWFuZElkZW50aWZpZXIiLHsiZGVwbG95bWVudElkIjoiQ29kZURlcGxveS91cy1lYXN0LTEvUHJvZC9hcm46YXdzOnNkczp1cy1lYXN0LTE6Mzc3NzAzOTYxOTk4OmRlcGxveW1lbnQvZC1VOVFPR0RBWUkiLCJob3N0SWQiOiJhcm46YXdzOmVjMjp1cy1lYXN0LTE6Mzc3NzAzOTYxOTk4Omluc3RhbmNlL2ktZWNmYzU1YTkiLCJjb21tYW5kTmFtZSI6Ikluc3RhbGwiLCJjb21tYW5kUG9zaXRpb24iOjQsImNvbW1hbmRBdHRlbXB0IjoxfV0=")
2016-11-10 07:38:12 ERROR [codedeploy-agent(16889)]: InstanceAgent::Plugins::CodeDeployPlugin::CommandPoller: Error during perform: RuntimeError - File already exists at location /var/cake_1.2.0.6311-beta/deployment/serverLoad.json - /opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:115:in `generate_normal_copy'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:67:in `block (2 levels) in generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:55:in `each'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:55:in `block in generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/install_instruction.rb:68:in `generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:54:in `generate_instructions'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/installer.rb:34:in `install'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_executor.rb:114:in `block in <class:CommandExecutor>'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_executor.rb:62:in `execute_command'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_poller.rb:132:in `process_command'
/opt/codedeploy-agent/lib/instance_agent/plugins/codedeploy/command_poller.rb:65:in `perform'
/opt/codedeploy-agent/lib/instance_agent/agent/base.rb:28:in `run'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:38:in `block in run'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:55:in `with_error_handling'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:37:in `run'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:70:in `block in run_with_error_handling'
/opt/codedeploy-agent/lib/instance_agent/runner/child.rb:55:in `with_error_handling'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:69:in `run_with_error_handling'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:33:in `block in start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:22:in `loop'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/child.rb:22:in `start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:206:in `block in spawn_child'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:204:in `fork'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:204:in `spawn_child'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:196:in `block in spawn_children'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:195:in `times'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:195:in `spawn_children'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:134:in `start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:37:in `block in start'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:36:in `fork'
/opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/master.rb:36:in `start'
/opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:41:in `block (2 levels) in <main>'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/command_support.rb:130:in `call'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/command_support.rb:130:in `execute'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:262:in `block in call_command'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:275:in `call'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:275:in `call_command'
/opt/codedeploy-agent/vendor/gems/gli-2.5.6/lib/gli/app_support.rb:69:in `run'
/opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:88:in `<main>'
更新 2
我能够通过重命名 json 文件并删除 appspec.yml 中的旧文件引用来应用脏修复。但是，在新的部署组（带有新的 ec2 实例）上，新的 json 文件导致相同的文件退出问题。每次改文件名都很痛苦。对正在发生的事情感到非常恼火。
作为其流程的一部分，CodeDeploy 将查找有关 app/deployment 组先前部署文件的信息。 If then it uses this info to delete existing files, preparing for deployment for new revisions, as needed.
http://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-steps.html#deployment-rollback
在这种情况下，由于您之前可能进行了手动清理，因此存在一些不一致的引用。
对于所有部署来说，一个不错的选择是在 BeforeInstall 挂钩期间简单地删除部署文件夹中的所有文件。这将解决现在和以后的问题。
这是可以解决的。 Codedeploy 对其自身未部署的文件抛出错误。但是有一个选项可以在部署期间覆盖它。
"内容选项： 当目标实例上的文件与应用程序修订中的文件同名且目标位置相同时，选择 AWS CodeDeploy 在部署期间采取的操作。"
您可以选择失败、覆盖和保留。这取决于你的情况。
您可以找到更多信息
docs.aws.amazon.com（奇怪在'rollback'下）
cli docs.aws.amazon.com（参见 --file-exists-behavior（字符串））