Ronelle Landy created DTACLOUD-503:
--------------------------------------
Summary: Digitalocean: GET /api/realms/realm_id always returns the
first realm
Key: DTACLOUD-503
URL: https://issues.apache.org/jira/browse/DTACLOUD-503
Project: DeltaCloud
Issue Type: Bug
Components: Native/Frontend
Environment: Deltacloud commit version:
d98dad812575d4e6b93396f7db226ac60e310077
Reporter: Ronelle Landy
Note the output of querying the two realms available:
This realm reports: NY - that's correct
>> curl -X GET --user "un:pw" "http://localhost:3001/api/realms/1?format=xml";
<?xml version='1.0' encoding='utf-8' ?>
<realm href='http://localhost:3001/api/realms/1' id='1'>
<name>New York 1</name>
<state>AVAILABLE</state>
</realm>
This time it should be Amsterdam ... but no, we're still in NY
>> curl -X GET --user "un:pw" "http://localhost:3001/api/realms/2?format=xml";
<?xml version='1.0' encoding='utf-8' ?>
<realm href='http://localhost:3001/api/realms/1' id='1'>
<name>New York 1</name>
<state>AVAILABLE</state>
</realm>
In test form ...
[root@qeblade39 deltacloud]# ruby realms_test.rb
Run options: --seed 13874
# Running tests:
.............F
Finished tests in 8.917125s, 1.5700 tests/s, 4.2615 assertions/s.
1) Failure:
test_0008_must have the "name" element for the realm and it should match with
the one in collection(Deltacloud API realms collection::collection member
common tests for realms)
[/home/dcloud/workspace/deltacloud/tests/deltacloud/common_tests_collections.rb:124]:
Expected: "Amsterdam 1"
Actual: "New York 1"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
