[5.7.80] Unable to list VMs in sunstone

(Edouard (Madko)) #1


after upgrade to 5.7.80, the vms tab in admin view seems broken. No vms are shown.

here is the log:

action.js:205 TypeError: graphics.TYPE.toLowerCase is not a function
    at Object.isVNCSupported (vm.js:841)
    at Object._elementArray [as elementArray] (datatable-common.js:52)
    at Table._elementArray [as elementArray] (datatable.js:122)
    at Object.<anonymous> (tab-datatable.js:607)
    at Function.each (jquery.js:365)
    at Table._updateView [as updateView] (tab-datatable.js:606)
    at callback (common-actions.js:46)
    at Object.success (action.js:203)
    at fire (jquery.js:3187)
    at Object.fireWith [as resolveWith] (jquery.js:3317)
success @ action.js:205
fire @ jquery.js:3187
fireWith @ jquery.js:3317
done @ jquery.js:8785
(anonymous) @ jquery.js:9151
load (async)
send @ jquery.js:9170
ajax @ jquery.js:8684
list @ action.js:173
list @ vm.js:365
_runAction @ sunstone.js:896
onShow @ dashboard-tab.js:76
(anonymous) @ dashboard-tab.js:237
each @ jquery.js:365
_onShow @ dashboard-tab.js:235
_runAction @ sunstone.js:937
_routerShowTab @ sunstone.js:694
(anonymous) @ sunstone.js:1257
resolve @ tips.js:41
_setupNavigoRoutes @ sunstone.js:1267
(anonymous) @ app.js:50
fire @ jquery.js:3187
add @ jquery.js:3246
jQuery.fn.ready @ jquery.js:3496
(anonymous) @ app.js:41
main @ almond.js:314
callDep @ almond.js:180
main @ almond.js:305
(anonymous) @ almond.js:388
setTimeout (async)
req @ almond.js:387
(anonymous) @ main.js:353

Any idea ?

onevm list works fine though

I’m using CentOS 7 packages.

Best regards,

(Anton Todorov) #2

Hi @madko,

There is no migration yet. As stated in the last paragraph of the OpenNebula 5.8 beta anouncement :

The OpenNebula team is now transitioning to “bug-fixing mode”. Note that this is a beta release aimed at testers and developers to try the new features, and send a more than welcomed feedback for the final release. Also note that being a beta, there is no migration path from the previous stable version (5.6.1) nor a migration path to the final stable version (5.8.0). A list of open issues can be found in the GitHub development portal.

To try the new features you should do a fresh install.

Best Regards,
Anton Todorov

(Edouard (Madko)) #3

Since I’m using 5.6.2 (and not 5.6.1) I thought there were a migration. At least onedb upgrade doesn’t complain.
I will try with an empty database. Thanks

(Edouard (Madko)) #4

Ok so with a fresh install, I can’t deploy a VM:

Sun Feb  3 13:41:47 2019 [Z0][ReM][E]: Req:976 UID:0 one.template.instantiate result FAILURE [one.template.instantiate] Error allocating a new virtual machine template. Missing clusters. Datastore for DISK 0 is not in any cluster

I don’t quite understand why, since all my datastores are by default in cluster 0:

 2 oneadmin   oneadmin   files                 8G 54%   0                 0 fil  fs      ssh     on 
 1 oneadmin   oneadmin   default            29.4G 93%   0                 1 img  fs      ssh     on 
 0 oneadmin   oneadmin   system                 - -     0                 0 sys  -       ssh     on 

I try to force deploy on a specific host and datastore, same results.

VM is a template from marketplace “CentOS 7 - KVM”.

Any idea why ?

(Alejandro Huertas) #5

Hello Edouard,

I have done some tests and it works for me.

So please, could you send me the template you are using? (onetemplate show <TEMPLATE_ID> -x)

I will try to reproduce your issue and fix it.


(Edouard (Madko)) #6

Hello Alejandro,

here is the template of this VM :

  <NAME>CentOS 7 - KVM</NAME>

Image template is here https://paste.fedoraproject.org/paste/M2sk7x27MAf3Nx71As0TTg/

Both are from the marketplace.

My admin.yaml view settings https://paste.fedoraproject.org/paste/gQ-r~5c2cAUw91R0OPtfbQ/ but I will try with the default file. Should not be relevant with the missing clusters.

(Alejandro Huertas) #7

Hello Edouard,

I can’t still reproduce your issue. So, if you can give me more information I will try to reproduce it again, but I’m afraid I won’t be able to.

Also, please try to instantiate the template using the CLI, does the error happen again?