AbelC
22
Hi @Pascal,
Before running the script, I need you to import the vCenter templates.
When you see something similar, run it. And it would help if you showed me the problematic templates like @ybizeul did.
Thanks!
Abel.
Pascal
(Pascal Kessler)
23
Hi @AbelC,
thanks, thats what i already did. But im not getting any similar information like @ybizeul does.
Filtering the reslut, i can see the text messages, which we already saw before in sunstone gui.
Best regards!
Pascal
ybizeul
(Yann Bizeul)
24
Can we provide more info? Or is there a workaround?
AbelC
25
Hi all,
Sorry for the late response.
The only solution I see to be able to continue with this is:
- Install opennebula from source.
- change proc -> dev in sunstone-server.conf
- debugge in chrome/firefox:
- Breakpoint in app/utils/vcenter/templates.js (line 496). So we can see that it sends Sunstone to the vCenter driver.
- Import vCenter template.
- When we are in the breakpoint, look that contains the variable ‘vcenter_ref’.
With this, we can detect in which layer the problem is. (Sunstone or vCenter driver).
Thanks.
Best regards,
Abel.