[
https://issues.apache.org/jira/browse/DTACLOUD-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oved Ourfali updated DTACLOUD-394:
----------------------------------
Description:
When working with the ovirt driver, setting the API_PROVIDER to
API_PROVIDER="http://server:port/api;;USER"; (to make it work with the
user-level API
And trying to create a VM via CIMI, it fails because:
1. rbovirt just takes the first cluster by name
2. Users aren't allowed to get a cluster by name (should be fixed)
See oVirt bug:
https://bugzilla.redhat.com/show_bug.cgi?id=876460
was:
When working with the ovirt driver, setting the API_PROVIDER to
API_PROVIDER="http://server:port/api;;USER"; (to make it work with the
user-level API
And trying to create a VM via CIMI, it fails because:
1. rbovirt just takes the first cluster by name
2. Users aren't allowed to get a cluster by name (should be fixed)
See oVirt bug:
> Tracking ovirt bug: Creating a VM via CIMI when using ovirt user-level API
> fails
> --------------------------------------------------------------------------------
>
> Key: DTACLOUD-394
> URL: https://issues.apache.org/jira/browse/DTACLOUD-394
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: Latest upstream code with User-level API
> Reporter: Oved Ourfali
>
> When working with the ovirt driver, setting the API_PROVIDER to
> API_PROVIDER="http://server:port/api;;USER"; (to make it work with the
> user-level API
> And trying to create a VM via CIMI, it fails because:
> 1. rbovirt just takes the first cluster by name
> 2. Users aren't allowed to get a cluster by name (should be fixed)
> See oVirt bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=876460
--
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
