Bug #331
Elastichosts driver triest to speak xml to Elastichosts and receives "Bad Operation"
Status: | Closed | Start date: | 08/27/2010 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | Javi Fontan | % Done: | 0% | |
Category: | Drivers - Auth | |||
Target version: | Release 2.0 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: |
Description
It's not possible to create a vm in Elastichosts at the moment.
Monitoring Elastichosts works. Trying to create a vm in Elastichosts fails with "Bad Operation" due to Opennebula trying to send an xml string which Elastichosts does not understand (that is what they see in the logs). I Confirmed elastichosts script itself is working by manually executing:
input-file: name bitrot cpu 500 mem 500 ide:0:0 <existing drive-uuid> boot ide:0:0 nic:0:model e1000 nic:0:dhcp auto vnc:ip auto vnc:password password # elastichosts -c -v -f input-file servers create
Manually executing
# elastichosts -v -f $ONE_LOCATION/var/15/deployment.0 servers create
leads to:
- Server auth using Basic with user 'XXXX'
POST /servers/create HTTP/1.1
Authorization: Basic XXXX
User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5
OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
Host: api.lon-p.elastichosts.com
Accept: */*
Content-Type: application/octet-stream
Content-Length: 230
<Server: BaseHTTP/0.3 Python/2.5.2
<Date: Wed, 18 Aug 2010 08:41:16 GMT
<X-Elastic-Error: usage
<Connection: close
<Content-Type: text/plain
Bad operation
- SSLv3, TLS alert, Client hello (1):
Closing connection #0 - SSLv3, TLS alert, Client hello (1):
History
#1 Updated by Tino Vázquez almost 11 years ago
- File ehmode.tar.gz added
Attaching a patch to create plain text EH compatible deployment files.
#2 Updated by Ruben S. Montero almost 11 years ago
- Status changed from New to 3
- Resolution set to fixed
#3 Updated by Ruben S. Montero almost 10 years ago
- Status changed from 3 to Closed