The following bugs or issues have been identified in the current 3.8 version, and will be solved in future releases.
OpenNebula 3.8.1 (Solved in 3.8.3)
#1564: If onedb finds the file where the backup is done in use, it won't do a new backup, but will restore the file nonetheless. This destroys the current DB contents.
<xterm>
$ onedb upgrade -v -S localhost -u oneadmin -p oneadmin -d opennebula
…
MySQL dump stored in /var/lib/one/mysql_localhost_opennebula.sql
…
$ mv /var/lib/one/mysql_localhost_opennebula.sql /my/backups/
</xterm>
#1619: TM VMFS delete and mvds scripts do not correctly set the DST_HOST variable, so the action works. Please apply the patch attached to the ticket to fix the issue for 3.8.1.
#1593: Shared TM drivers in VMware based clouds do not manage correctly the persistency of files. Please apply the patch attached to the ticket to fix the issue for 3.8.1.
OpenNebula 3.8.3
#1724: oZones doesn't run properly on Debian 6 due to the json gem not supporting “convert to symbol” feature. Applies to 3.8.3.
-
#1754: For Ubuntu and Debian
onemarket
installs under
/use/bin/onemarket
. To fix this do:
$ sudo mv /use/bin/onemarket /usr/bin; sudo rmdir /use/bin
.
#1806: Incorrect log path for Sunstone in system wide installation. To fix apply this patch to this file: /usr/lib/one/sunstone/models/SunstoneServer.rb
and restart Sunstone.
OpenNebula 3.8.4
#2134: Self-service portal timeouts in 5s
OpenNebula 3.8.5
In large environments, the default xmlrpc server used by OpenNebula comes with a fixed number of current sockets that can make OpenNebula slow in answering requests. If you are running such a large scale environment, you can compile OpenNebula 3.8.5 against a newer version of xmlrpc that is able to be configured using a special set of parameters. More information in
this ticket.