[
https://issues.apache.org/jira/browse/DTACLOUD-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh A updated DTACLOUD-115:
------------------------------
Environment:
Deltacloud API 0.4.1
OS- Fedora 15
API_PROVIDER=vsphere.virt.bos.redhat.com
VMware vSphere 4
commit 9ce0222c3b88ac83a676f948a99ee07aa0f24b3c
[root@cavenger ~]# rpm -qa | grep deltacloud
deltacloud-core-rhevm-0.4.1-8.fc15.noarch
deltacloud-core-vsphere-0.4.1-8.fc15.noarch
deltacloud-core-ec2-0.4.1-8.fc15.noarch
rubygem-deltacloud-client-0.4.0-3.fc15.noarch
deltacloud-core-0.4.1-8.fc15.noarch
was:
Deltacloud API 0.4.1
OS- Fedora 15
commit 9ce0222c3b88ac83a676f948a99ee07aa0f24b3c
[root@cavenger ~]# rpm -qa | grep deltacloud
deltacloud-core-rhevm-0.4.1-8.fc15.noarch
deltacloud-core-vsphere-0.4.1-8.fc15.noarch
deltacloud-core-ec2-0.4.1-8.fc15.noarch
rubygem-deltacloud-client-0.4.0-3.fc15.noarch
deltacloud-core-0.4.1-8.fc15.noarch
> Duplication in starting an image on VSphere, neither creates a new instance
> nor displays any error message related to this
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-115
> URL: https://issues.apache.org/jira/browse/DTACLOUD-115
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby)
> Environment: Deltacloud API 0.4.1
> OS- Fedora 15
> API_PROVIDER=vsphere.virt.bos.redhat.com
> VMware vSphere 4
> commit 9ce0222c3b88ac83a676f948a99ee07aa0f24b3c
> [root@cavenger ~]# rpm -qa | grep deltacloud
> deltacloud-core-rhevm-0.4.1-8.fc15.noarch
> deltacloud-core-vsphere-0.4.1-8.fc15.noarch
> deltacloud-core-ec2-0.4.1-8.fc15.noarch
> rubygem-deltacloud-client-0.4.0-3.fc15.noarch
> deltacloud-core-0.4.1-8.fc15.noarch
> Reporter: Ramesh A
> Assignee: David Lutterkort
>
> Duplication in starting an image on VSphere, neither creates a new instance
> nor displays any error message related to this
> Reproduction Steps:
> ===============
> 1. Start an Instance with the name "test-setup" with the available images
> 2. Once the above instance is started and running successfully, start another
> instance with the same name and same configuration as used in the previous
> step
> Expected Result:
> =============
> Should start a new instance or should throw error message stating cannot
> start the instance as another instance is running with the same name
> Actual Result:
> ===========
> 1. Seems that the second instance is not getting started
> 2. The Instance Details output page which is rendered displays the first
> instance details
--
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
