Bug #1996: Unable to edit user VM quotas from Sunstone - OpenNebula - OpenNebula Development pages

Bug #1996

Unable to edit user VM quotas from Sunstone

Added by Simon Boulet about 8 years ago. Updated about 8 years ago.

Status:

Closed

Start date:

05/03/2013

Priority:

Normal

Due date:

Assignee:

Daniel Molina

% Done:

100%

Category:

Sunstone

Target version:

Release 4.2

Resolution:

fixed

Pull request:

Affected Versions:

OpenNebula 4.0

Description

I don't seems to be able to edit my users maximum number of VM from Sunstone (latest RC tarball).

From the Update Quota window, I click the Pencil /Edit icon right of the "VM" line, then enter the new limit on the left input box, hit the Add/edit button. I can see the new limit has been appended to the bottom of the quota list on the right. The I click Apple changes (nothing seems to happen clicking that button) then Close. Hit refresh to confirm the new quota, and still sees the old quota.

For information I am trying to set:
VMs: 9.
Memory: -1 MB.
CPU: -1.

I suppose -1 is for unlimited?

Thanks

Simon

History

#1 Updated by Simon Boulet about 8 years ago

Note I have no problem updating the quota from the cli (oneuser quota)

#2 Updated by Daniel Molina about 8 years ago

I cannot reproduce the problem. What browser are you using? Could you check if there is any error in the browser console after clicking the apply changes button? The form should fade out after clicking this button.

#3 Updated by Simon Boulet about 8 years ago

Chrome 26.0.1410.63 on Linux.

I am seeing a bunch of "JQMIGRATE: jQuery.fn.toggle(handler, handler...) is deprecated " warnings in the Javascript console (seems to happen when I initially load the Sunstone dashboard, nothing particular when trying to update the quotas).

#4 Updated by Daniel Molina about 8 years ago

Same problem if you update the group quota instead of the user quota?

#5 Updated by Simon Boulet about 8 years ago

Yes, same problem. The "Apply changes" button doesn't seems to do anything. Nothing in the javascript console. I suppose there are simply no trigger bounded to the "Apply changes" button.

#6 Updated by Daniel Molina about 8 years ago

Yes, it looks like there is a problem with the event. What's the name of the package you installed?

#7 Updated by Simon Boulet about 8 years ago

My frontend runs CentOS, I previously had the CentOS-6.4 3.9.80-1.0 opennebula-ruby, opennebula-common and opennebula-sunstone packages installed. I noticed a new 3.9.90-2 package was out, and just did the upgrade.

I'm still unable to edit users (or groups) quota. However now when hitting the Apply changes button (after editing the maximum number of VM for user from 8 to 9), I can see my browser being redirected to http://myfrontend:9869/?quota_type=vm&VMS=9&MEMORY=-1&CPU=-1&ID=1&SIZE=&IMAGES=&ID=&RVMS=&ID=&LEASES=

I had to manually upgrade Ruby after running into the issues described here: http://www.mail-archive.com/users@lists.opennebula.org/msg10226.html

I am currently running ruby 1.9.3p286 (2012-10-12 revision 37165).

/usr/share/one/install_gems
Gems already installed

Gems list:

amazon-ec2 (0.9.17)
bigdecimal (1.1.0)
curb (0.8.3)
daemon_controller (1.1.4)
daemons (1.1.9)
eventmachine (1.0.3)
fastthread (1.0.7)
io-console (0.3)
json (1.5.4)
minitest (2.5.1)
mysql (2.9.1)
net-ldap (0.3.1)
nokogiri (1.5.9)
passenger (3.0.19)
rack (1.5.2)
rack-protection (1.5.0)
rake (0.9.2.2)
rdoc (3.9.4)
sequel (3.47.0)
sinatra (1.4.2)
sqlite3 (1.3.7)
thin (1.5.1)
tilt (1.4.0)
uuidtools (2.1.4)
xml-simple (1.1.2)

#8 Updated by Ruben S. Montero about 8 years ago

Category set to Sunstone
Assignee set to Daniel Molina
Target version set to Release 4.2

#9 Updated by Simon Boulet about 8 years ago

Hi Daniel

I have just updated to release-4.0 and everything is working now.