[
https://issues.apache.org/jira/browse/JCLOUDS-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Turli updated JCLOUDS-1150:
----------------------------------
Fix Version/s: (was: 1.9.3)
2.0.1
> Resource not ready error deploying to gce location
> --------------------------------------------------
>
> Key: JCLOUDS-1150
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1150
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.9.2
> Reporter: Duncan Grant
> Assignee: Andrea Turli
> Labels: google-compute-engine
> Fix For: 2.1.0, 2.0.1
>
>
> Deploying to google compute engine get an error from the GCE api -
> "message": "The resource
> 'projects/jclouds-gce/global/networks/jclouds-qa-now-scheduler-etcd-node' is
> not ready"
> I was provisioning compute nodes through brooklyn and I can't replicate this
> error very reliably so not sure what the exact details are. Will update bug
> when I find out more.
> Error invoking start at EtcdClusterImpl{id=ul9r7gy16e}: Node in cluster
> EtcdClusterImpl{id=ul9r7gy16e} failed: Error invoking start at
> EtcdNodeImpl{id=pj0xe55sk9}: HttpResponseException: command: POST
> https://www.googleapis.com/compute/v1/projects/jclouds-gce/global/firewalls
> HTTP/1.1 failed with response: HTTP/1.1 400 Bad Request; content: [{
> "error": {
> "errors": [
> {
> "domain": "global",
> "reason": "resourceNotReady",
> "message": "The resource
> 'projects/jclouds-gce/global/networks/jclouds-qa-now-scheduler-etcd-node' is
> not ready"
> }
> ],
> "code": 400,
> "message": "The resource
> 'projects/jclouds-gce/global/networks/jclouds-qa-now-scheduler-etcd-node' is
> not ready"
> }
> }
> ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
