[
https://issues.apache.org/jira/browse/JCLOUDS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889079#comment-13889079
]
Ignasi Barrera commented on JCLOUDS-445:
----------------------------------------
These are separate topics: One thing is the node provisioning, and another one
is the result of executing a script on it.
Currently jclouds creates a node in a cloud provider and gives the possibility
to run "an arbitrary script" in the node. That script may be executed just when
booting the machine, but it could be run afterwards (even periodically) with
the ComputeService.runScriptOnNode. In the latter case, it makes little sense
to mark the node as failed.
One thing is the state of the node, which determines if the node exist or not
in the cloud provider, and if it is running, and another different thing is the
result of executing a (arbitrary) script one the node.
If you want to take some action (such as rolling back the node) upon script
execution failure, the right approach is to retrieve the
[ExecResponse|https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/domain/ExecResponse.java]
object for the script execution and act according to the returned status.
> bootstrap script should fail the create vm if it has errors
> -----------------------------------------------------------
>
> Key: JCLOUDS-445
> URL: https://issues.apache.org/jira/browse/JCLOUDS-445
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.7.0, 1.8.0
> Reporter: Izek Greenfield
> Labels: bootstrap-script, jclouds
>
> I see error in the bootstrap script and Jclouds return the machine as OK.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
