deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DTACLOUD-274) CIMI: /cimi/networks/<network id>/stop returns successful (200 code) but the network state is still "started"
Date Wed, 11 Jul 2012 19:31:33 GMT
Ronelle Landy created DTACLOUD-274:
--------------------------------------

             Summary: CIMI: /cimi/networks/<network id>/stop returns successful (200
code) but the network state is still "started"
                 Key: DTACLOUD-274
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-274
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server
         Environment: deltacloud git commit: 714c474d240945ec07f39873bac148ce966a2246
mock provider
Fedora 16
            Reporter: Ronelle Landy


Started deltacloud using the cimi frontend, targeting the mock provider:
>> ./bin/deltacloudd -i mock -f cimi -r <hostname> -p 3006

Following the examples posted here: http://mariosandreou.com/deltacloud/cloud_API/2012/04/06/cimi-networks-deltacloud.html,
I tried to stop a network ... 

************************************

[rlandy@localhost ~]$ curl -iv -X POST --user "mockuser:mockpassword" -H "Content-Type: application/xml"
-d '<Action xmlns="http://www.dmtf.org/cimi"> <action> http://www.dmtf.org/cimi/action/stop
</action> </Action> ' "http://dell-pe2900-02.rhts.eng.bos.redhat.com:3006/cimi/networks/network2/stop?format=xml"

* About to connect() to dell-pe2900-02.rhts.eng.bos.redhat.com port 3006 (#0)
*   Trying 10.16.64.129... connected
* Connected to dell-pe2900-02.rhts.eng.bos.redhat.com (10.16.64.129) port 3006 (#0)
* Server auth using Basic with user 'mockuser'
> POST /cimi/networks/network2/stop?format=xml HTTP/1.1
> Authorization: Basic bW9ja3VzZXI6bW9ja3Bhc3N3b3Jk
> User-Agent: curl/7.21.7 (x86_64-redhat-linux-gnu) libcurl/7.21.7 NSS/3.13.1.0 zlib/1.2.5
libidn/1.22 libssh2/1.2.7
> Host: dell-pe2900-02.rhts.eng.bos.redhat.com:3006
> Accept: */*
> Content-Type: application/xml
> Content-Length: 108
> 
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Content-Type: text/html;charset=utf-8
Content-Type: text/html;charset=utf-8
< X-Frame-Options: sameorigin
X-Frame-Options: sameorigin
< X-XSS-Protection: 1; mode=block
X-XSS-Protection: 1; mode=block
< X-CIMI-Specification-Version: 1.0.0
X-CIMI-Specification-Version: 1.0.0
< Date: Wed, 11 Jul 2012 16:21:28 GMT
Date: Wed, 11 Jul 2012 16:21:28 GMT
< Content-Length: 0
Content-Length: 0
< Connection: keep-alive
Connection: keep-alive
< Server: thin 1.4.1 codename Chromeo
Server: thin 1.4.1 codename Chromeo
< 
* Connection #0 to host dell-pe2900-02.rhts.eng.bos.redhat.com left intact
* Closing connection #0

*******************************

The above command returns a 200 code (which looks like the stop should have been successful)
but querying the network shows the state as STARTED:

[rlandy@localhost ~]$ curl -X GET --user "mockuser:mockpassword" "dell-pe2900-02.rhts.eng.bos.redhat.com:3006/cimi/networks/network2?format=xml"

<Network xmlns="http://www.dmtf.org/cimi">
  <maxTrafficJitter>200000</maxTrafficJitter>
  <trafficPriority>2</trafficPriority>
  <bandwidthLimit>3</bandwidthLimit>
  <description>another network</description>
  <id>http://dell-pe2900-02.rhts.eng.bos.redhat.com:3006/cimi/networks/network2</id>
  <state>STARTED</state>
  <name>network2</name>
  <created>Fri Jan 13 17:30:34 EET 2012</created>
  <routingGroup href="http://dell-pe2900-02.rhts.eng.bos.redhat.com:3006/cimi/routing_groups/group1"
/>
  <operation href="http://dell-pe2900-02.rhts.eng.bos.redhat.com:3006/cimi/networks/network2"
rel="edit" />
  <operation href="http://dell-pe2900-02.rhts.eng.bos.redhat.com:3006/cimi/networks/network2"
rel="delete" />
  <maxTrafficLoss>100</maxTrafficLoss>
  <maxTrafficDelay>600000</maxTrafficDelay>
  <access>Public</access>
</Network>
[rlandy@localhost ~]$ 

*********************************

I tried the curl stop command with and without the -d ' ....' arguments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message