Known Issues 3.0
The following bugs or issues have been identified in the current 3.0 version, and will be solved in future releases.
The x509 authentication fails if the certificates contain certain characters, like the colon (:), or accented letters (e.g. á, ö).
There is a bug that rarely causes OpenNebula to show a wrong number of running VMs in a host. The dev team is unable to reproduce this problem and will appreciate any feedback on this.
If the request is submitted with all the available VM disks, and on of them has a previous SAVE_AS tag and is not removed, the server will fail. The server would need to compare and ignore old SAVE_AS.
Under some MySQL backend and character encoding configurations, OpenNebula fails to create the DB tables the first time it starts. You will find in /var/log/one/oned.log messages similar to this one:
Specified key was too long; max key length is 767 bytes
You can use instead the default SQLite DB. Alternatively, the following bug description contains a workaround; basically you need to create the same tables with fewer characters for some text columns:
The ACL rules affecting a group or user are left behind when those are deleted. This doesn't cause any malfunction since the IDs are not reused, but it would be easier to manage the ACL rules if they are automatically cleaned.
Disabled users are allowed to login in sunstone. Then, as expected, it fails to retrieve any resources with “User could not be authenticated” message, but they shouldn't be allowed to log in the first place.
Wrong deployment file created during the deployment of a VM based on a virtual machine template with a floppy disk image mapped.
The scheduler filters the existing hosts to get the ones with a status less than 3, including the ones in INIT or MONITORING state. A Host in MONITORING state may be chosen to deploy a VM if there is old monitoring data in it, but the host may be unreachable and end in ERROR state.
Creating a machine template with certain characters (angle brackets for instance) disrupts the correct behavior.
Suspend fails when the checkpoint file already exists. A different checkpoint file should be use each time a VM is suspended.
With the Gangdia monitor, if the VM is no longer running, the last valid report will remain effective so that it will always show that VM as in RUNNING state.
It seems that some versions of libvirt does not honor the target attribute for libvirt.
There is a bug using xml templates that defines their elements in more than one line.
If the target directory is not clean and images directory exists then a new images directory will appear inside old images dir. Restore of that VM will crash as the files are not in the place oned thinks they are. This directory should be deleted before moving.
The DB connection details for onedb are read by default from oned.conf. The user can optionally supply these connection parameters using command line options, but there is a bug that causes the MySQL options '-u', '-p' and '-d' to be ignored.
The workaround is to use the oned.conf file to specify these parameters.