Making any user config change resets VNC_WSS to 'no' PATCH INCLUDED
|Assignee:||Daniel Molina||% Done:|
|Category:||Sunstone||Estimated time:||0.10 hour|
|Target version:||Release 5.0|
|Affected Versions:||OpenNebula 4.12, OpenNebula 4.14|
Revision 4c6e4986 removed the VNC encryption checkbox from the config tab UI, but the code using it to set vnc_wss remained. As a result, switching to a different Sunstone view flipped off encryption so VNC seemed to not work in the newly-chosen view.
The included patch is very simple: removes 6 lines (one empty) from one file in the 4.12 branch. This part of Sunstone has apparently been entirely refactored for 4.14, so it is likely not relevant to the trunk.
Bug #4357: Do not retrieve VNC_WSS from the USER template
(cherry picked from commit 2834b2a8f0f135d890dc44d587e2e36af3385293)
#1 Updated by Daniel Molina about 5 years ago
- Status changed from Pending to New
- Assignee set to Daniel Molina
- Target version set to Release 5.0
- Affected Versions OpenNebula 4.14 added
Thank you for the patch, as you mentioned it doesn't apply for one-4.14 since that code was removed/refactored.
That code should not modify the VNC wss configuration, but the problem is this other line in sunstone-server.rb that should also be removed from both one-4.12 and one-4.14, since the VNC wss configuration is retrieved from the server config file