rohdoor / ovz-web-panel

Automatically exported from code.google.com/p/ovz-web-panel
Other
0 stars 0 forks source link

Synchronization causing unlimited RAM #538

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Steps to reproduce:
1. Synchronize server in web panel, causing all containers to have unlimited 
RAM (in panel only, not inside CT)
2. Change package/server template in panel, causes CT itself to have unlimited 
RAM applied to it as well due to step 1.
3. Set any value to RAM, then change package/server template again to get 
actual values needed within CT itself.

Actual result: RAM goes to unlimited in panel upon synchronization, and 
subsequent saves of CT settings changes within panel causes unlimited RAM 
within CT itself, unless value applied manually to RAM then package changed 
again. Web Panel continues to show old data after package/server template 
change as well. Panel only updates if changes are made to additional settings 
section, and not with package change.

Expected result: RAM should not set to unlimited within the panel after 
synchronization. Also, upon changing package/server template, all details in 
additional settings section should update simultaneously, this would allow Web 
Panel to also update its values shown in the web panel after a package/server 
template change, so that you always know by looking at the panel what its set 
to, without actually having to "free -m" within the CT itself for example.

Version of the product: 2.4

Server OS: CentOS 6.5

Browser: Firefox

Additional information:

Original issue reported on code.google.com by 86brown on 3 May 2014 at 9:48

GoogleCodeExporter commented 9 years ago
Tested some more, this does not appear to be an issue with synchronization, my 
apologies. Really the only issue here is the web panel showing non-updated 
values after changing server template/package.

All other written above can be ignored. The panel issue has already been 
reported a little bit below mine so this issue #538 can be removed.

Original comment by 86brown on 3 May 2014 at 10:10