OpenNebula 3 SP2 (3.8.5) - Incremental Release Notes

Oct 25th, 2013. The OpenNebula Project announces the general availability of the second Service Pack for the OpenNebula 3 Series (3.8.5). After its first year, and for two additional years, the Project distributes Service Packs (SP) for each major release that combine all the patches to easily install or deploy its last update. Service Packs allow users to maintain their current OpenNebula version as long as possible, preserving the stability and security of their data centers, as they transition from one OpenNebula Series to the next.

This is a maintenance release that fixes bugs reported by the community after 3.8.4 was released. This release only includes bug fixes and is a recommended update for everyone running any 3.x. Check out the OpenNebula 3.8 Twin-Jet release notes for the release highlights and a summary of the new features incorporated in OpenNebula 3.8.

Bugs Fixed in OpenNebula 3.8.5

Important bugs solved since 3.8.4 release include:

  • Bug #1688: Openvswitch brcompat deprecation issues
  • Bug #1563: New defaults for KVM driver
  • Bug #2045: Make VNC port be the first available from a range
  • Bug #2388: Broken resume action in EC2 drivers
  • Feature #2329: Add EBS optimized option to EC2 VMs
  • Bug #2352: Extend host share variables to better support hybrid deployments
  • Bug #2352: Extend host share variables to better support hybrid deployments
  • Bug #2134: Check occi-user cookie instead of one-user when using Selfservice
  • Fix error message when connecting to OpenNebula Marketplace

Bugs Fixed since OpenNebula 3.8.0

  • Bug #1673: Add support for 64-bit net_tx/net_rx counters
  • Bug #1721: VMware datastores doesn't handle non directories
  • Feature #1726: Pass custom information to .vmx file
  • Bug #1732: Fix -s & -e options for oneacct
  • Bug #1733: Change onehost update method rights to ADMIN
  • Bug #1740: Shutdown action only calls for system datastore
  • Bug #1777: EC2 server does not check SignatureVersion
  • Bug #1792: Problem with duplicated MACs on filtering with Open vSwitch
  • Bug #1794: Make vmware image registration more robust by allowing files other than .vmdk
  • Bug #1779: Handle error when the marketplace is not available
  • Bug #1805: LCM::monitor_suspend_action frees the host capacity
  • Bug #1810: Attach disk/nic needs to check the template format
  • Bug #1813: Change database to hold bigger objects
  • Bug #1816: regionEndpoint with missing hostname in DescribeRegions
  • Bug #1822: Missing context .isofiles directory cleanup
  • Bug #1861: LDAP user password exposed in oned.log
  • Bug #1867: VM migration to the same host is allowed, but it will break the Running VMs counter
  • Bug #1889: onedb fsck removes users quotas for VMS/MEMORY/CPU
  • Bug #1911: Broken VMware CDROM support
  • Bug #1914: Client installation does not install ssh_auth.rb
  • Bug #1917: Sunstone won't notice when a password is changed
  • Bug #1918: Oneuser key does not remove BEGIN PUBLIC KEY
  • Bug #1921: ssh and x509 login never expires
  • Bug #1923: Ozones should not use settings
  • Bug #1933: Broken vmfs delete (USE_SSH=no)
  • Bug #1948: Umask hardcoded in MVDS scripts
  • Bug #1966: Broken datastore_mad/vmware/rm for CDROMs
  • Bug #1983: NETWORK_ADDRESS should be left in the vnet template
  • Bug #1995: DATA_VMX not working when no OS disk
  • Bug #1997: Re implement VMware drivers VI API calls
  • Bug #2037: Check if session cookie has been changed
  • Bug #2104: Overwriting when attaching non-persistent disk
  • Bug #1669: Improve case sensitivity consistency
  • Bug #1668: XML parser fails to parse empty xml elements
  • Bug #1661: CLONE operation is broken for VMFS datastores with SSH connection enabled
  • Bug #1659: The core writes numbers in scientific notation
  • Bug #1593: failed: mv: cannot remove /vmfs/volumes/*: Is a directory
  • Bug #1119: onedb migrator 3.1.80 to 3.2.0 sets wrong uid & gid values in the DB (included in fsck)
  • Fix bug in host_on_error hook
  • Fix a bug the TM iscsi/delete action where it shouldn't remove the link
  • Fix log path for Sunstone in system wide installation
  • Retry kvm cancel to make sure the VM is destroyed
  • Multiple VMFS driver fixes
  • Fix rack problem with cloud servers and sunstone
  • Fix OpenNebula CentOS init script
  • Fix compilation for ruby > 1.9

Known Issue

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.

Migrating to OpenNebula 3.8.5

OpenNebula 3.8.5 is API compatible with OpenNebula 3.x, so you should expect that applications and drivers developed for 3.x work with this release.

Also there have been minor changes in the OpenNebula DB schema to accommodate big resource descriptions. These changes are automatically managed by the migration process, but if you have developed any customization you may need to update it.

A detailed upgrade process can be found in the documentation.

For a complete set of changes to migrate from a 3.x installation please refer to the Compatibility Guide. You should also read this document if you are an OpenNebula 3.x user.

Getting the Software

OpenNebula is released under the Apache 2.0 open source license. The complete source tree and binary packages for OpenNebula can be downloaded here.

Please report any bug or send feedback at the development portal or at the mailing list.

The documentation of OpenNebula 3.8 can be found here.


We'd like to thank the great feedback received, it is an essential part of the process that makes OpenNebula a reality, and the primary source of improvement. A detailed list of people that have contributed to OpenNebula 3.8, can be found in the Twin-Jet release notes

About OpenNebula

More information about the project can be found at the project web page. You may be also interested in checking the OpenNebula Ecosystem that includes many interesting projects contributed by the community to enhance or add new features to OpenNebula.