VMware Integrated OpenStack 1.0.2 Patch Release Notes

VMware Integrated OpenStack 1.0.2 | 15 JUNE 2015 | Build 2813500 (patch) | Build 2824223 (full install)

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes apply to VMware Integrated OpenStack 1.0.2 and cover the following topics:

Updated Registering the VMware Integrated OpenStack vApp

The icon for the VMware Integrated OpenStack vApp (VMware Integrated OpenStack Manager Service) might not appear after deploying the VMware Integrated OpenStack OVF. Usually, logging out and logging back resolves, but if it does not, you must manually register the vApp plugin.

To manually register the vApp plugin:

  1. Navigate to https://[VMware Integrated OpenStack Manager Service IP Address]:8443/register-plugin/login.jsp.

  2. Log in with the vCenter credentials.

  3. Under Status, locate the red status indicator showing that the management server is not correctly connected to the vCenter correctly.

  4. Click Fix.

  5. In the Certificate dialog box, verify the certificate and click OK.

  6. Log out from the registration interface.

  7. Log in to the vSphere Web Client.

    The VMware Integrated OpenStack Manager icon should now be visible in the vCenter Web Client.

Issues Resolved in this Patch

VMware Integrated OpenStack enables the rapid deployment of OpenStack on a VMware vSphere virtual platform. This release resolves the following issues.

  • Insufficient heap size can cause deployment to fail.
    Fixed in 1.0.2. Read VMware KB 2021302 to determine the best heap size configuration for your system.

  • Deployment fails because no DNS addressing is configured.
    Clarified when a DNS setting is required when configuring Networking.

  • Cluster status might be inaccurate.
    Fixed an issue where an OpenStack cluster shows a status of RUNNING in the vSphere Web Client even though some of the node VMs in a cluster are powered off.

  • Unable to create VSAN datastore.
    Fixed an issue where an error message resulted when a user tried to create a datastore in a nested ESXi instance using an OpenStack volume backed by VSAN.

  • Ability to Install Infrastructure Patches Through the VMware Integrated OpenStack Manager.
    You can now download and install patch releases using the VMware Integrated OpenStack Manager. (Previously, such patches could only be installed via the CLI.)

  • Creating a No-Disk Flavor Using the tiny-core.iso Image Causes Attribute Error.
    Resizing VMs with no root disk is now permitted, preventing the error.

  • Incorrect Management Server IP Address Appears on Patch Getting Started Page.
    The correct IP address now appears.

  • Duplicate Network Names in Multiple Datacenters in Same vCenter Causes VMware Integrated OpenStack to Fail.
    Network selection no longer relies on network name alone.

  • Orchestration stack fails when detaching multiple volumes and deleting multiple instances.
    The root cause was traced to an OpenStack error. By updating VMware Integrated OpenStack to the OpenStack 2014.1.4 release, this issue was fixed.

  • Orchestration performs very slowly when deleting fifty or more instances when each instance has a Cinder volume.
    Issue fixed, with orchestration performance improved.

  • Haproxy Log Not Collected by CLI Log Collection Command.
    Fixed the error that omitted this log file during the log collection process.

  • Provisioning Failure Caused By Inconsistent Resource Tracking.
    Fixed an error that resulted in misreported vCPU usage, which then caused provisioning failures.

  • Interminable Heat Stack VM Deletion.
    Fixed exception handling when static binding deletion was failing.

Open Source Components for VMware Integrated OpenStack 1.0.2

The copyright statements and licenses applicable to the open source software components distributed in VMware Integrated OpenStack 1.0.2 are available on the Open Source tab of the product download page. You can also download the source files for any GPL, LGPL, or other similar licenses that require the source code or modifications to source code to be made available for the most recent available release of VMware Integrated OpenStack.

Applying the Version 1.0.2 Patch

You upgrade to version 1.0.2 by installing a patch (1.0.2 Build 2813500) on version 1.0.0 or version 1.0.1.

The following procedures assume you have installed version 1.0.0 or 1.0.1. This patch updates the product UI and therefore must be installed using the CLI instructions documented below.

  1. Obtain the patch (Build

    • Log into the VMware Integrated OpenStack management server.

    • Download the debian file for the patch.

    • Add the patch with the following command:

      viopatch add -l [path to the debian file]

    • Confirm that the patch was successfully added:

      viopatch list

      This returns a list of available patches, their version numbers, their type, and current status. The list should include vio-patch-2

  2. Install the patch.

    • Ensure that VMware Integrated OpenStack service is either running or not yet deployed.

      If the VMware Integrated OpenStack service is in any other state, the upgrade will fail.

    • Log into the VMware Integrated OpenStack management server and run the following command:

      viopatch install --patch vio-patch-2 --version

      The patch installation takes 5 to 10 minutes to complete.

  3. To complete the update, log out of the vSphere Web Client and back in.

    You can ignore any error messages you encounter when logging back in.

  4. If necessary you can revert to version 1.0 by uninstalling Patch 2.

    • Log into the VMware Integrated OpenStack management server and run the following command:

      viopatch uninstall --patch vio-patch-2 --version

      The reversion process takes 5 to 10 minutes to complete.

    • After uninstalling the patch, you must restart the vSphere Web Client service on the vCenter Server to downgrade the VMware Integrated OpenStack plugin.

      Read VMware KB 2054085 to learn about restarting vCenter Server appliance services.

Troubleshooting the Patch Installation

The following list describes common problems you might encounter when installing the patch, and their solutions.

  • Error returned when using the vSphere Web Client to add patch.

    Add and install the patch using the CLI method described in Applying the Version 1.0.2 Patch.

  • Patch installation fails.

    Ensure that the OpenStack deployment is either running or not yet deployed. If it is running, ensure that all the OpenStack management VMs (memcache, loadbalancer, and so on) are also running.

    If you restart any of the VMs, run the vioconfig configure command on the OpenStack management server CLI and apply the patch again.

Updated Known Issues

VMware Integrated OpenStack 1.0.2 has the following known issues. If you encounter an issue that is not in this known issues list, search the VMware Knowledge Base, or let us know by contacting VMware Technical Support.

  • Unable to modify syslog setting post deployment in VIO Manager interface

    After deploying VIO, you cannot modify the syslog server configuration using the setting in the VIO Manager interface (VMware Integrated OpenStack>Management Server>(right-click and select) Edit Settings>vApp Options tab).

    Workaround: Modify the configuration here: VMware Integrated OpenStack>OpenStack Cluster>Manage (tab)>LogInsight.

  • Dashboard might show a Volume as attached even if it failed to attach.
    This is a known OpenStack issue, first reported in the Icehouse release.

  • Long image upload times cause NotAuthenticated failure.
    This is a known OpenStack issue (https://bugs.launchpad.net/glance/+bug/1371121), first reported in the Icehouse release.

  • Updated Host route injection doesn't work in VMware Integrated OpenStack 1.0.1
    This issue has been fast-tracked for resolution.

  • Volume extend fails if a shadow VM has a disk chain.
    The extend volume feature is not supported when the volume contains one or more snapshots.

  • OpenStack dashboard does not immediately reflect volume extension.
    If you extend the size of a volume, the dashboard might still display the pre-extended size. Eventually, the correct size appears.

  • False error alert displays during provisioning.
    When you accept the configuration settings and start the installation process, you might get an error alert even though the provisioning continues. This is a false error.

    Workaround: Refresh the browser.

  • CLI actions for stop/start not reflected in vSphere Web Client.
    If you use the CLI commands to stop or start the VMware Integrated OpenStack service, the service might still appear to be running in the vSphere Web Client even though the command was successful. For example, if you stop the service using the CLI command (vioconfig stop), you will not be able to access the VMware Integrated OpenStack dashboard.

    Workaround: Use the vSphere Web Client GUI commands to stop or start the VMware Integrated OpenStack service.

  • OpenStack Management Service does not restart after vSphere HA event.
    If vSphere experiences an HA event (for example, the ESXi host hosting the OpenStack Management Server), when vSphere HA restarts, the OpenStack Management Service remains is not restarted. Observed in vCenter Server Version 5.5.

    Workaround: If a vSphere HA event occurs that affect the OpenStack deployment, ensure that the OpenStack Management Service has restarted. Restart manually if necessary.

  • Database node failure might block access to the dashboard for up to thirty minutes.
    If the master database node fails and restarts, users may not be able to log in to VMware Integrated OpenStack dashboard (Horizon) for up to thirty minutes. Observed in vCenter Server Version 5.5.

  • Installer gives priority to local storage by default.
    When provisioning datastores for the three database VMs, the VMware Integrated OpenStack installer automatically gives priority to local storage to improve I/O performance. For resiliency, users might prefer shared storage, but the installer does not make it clear how to modify this setting.

    Workaround: Before you complete the installation process, the VMware Integrated OpenStack installer allows you to review and modify the configuration. You can use this opportunity to change the datastore configuration for the three database VMs.

  • Special characters in datastore names not supported by Glance (Image Service).
    If a datastore name has non-alphanumeric characters like colons, ampersands, or commas, the datastore cannot be added to the Glance service. Specifically, the following characters are not permitted in Glance datastore names because their use is reserved for other purposes and therefore can interfere with the configuration: : , / $ (colon, comma, forward slash, dollar).This issue has been fast-tracked for resolution.

  • Edge VMs require shared datastores.
    When you configure your Edge VMs, ensure that the cluster you select for Edge VMs has shared datastores. Without configuring shared datastores for that cluster, all the Edge VMs attach to the same local datastore of one ESXi host, limiting host selection and negatively affecting performance.

  • Nova boot creating a new volume from OVF fails.
    OVF is an unsupported format.

    Workaround: Convert the OVF to an OVA using the appropriate VMware tool or use another supported format.

  • Without NAT, firewall rules prevent external-to-internal communication.
    Without NAT/SNAT, inbound connectivity to OpenStack instances is blocked by the firewall.

    Workaround: Add a new firewall rule: "From: vNIC External" | "To: (Internal Networks: [network IP Address], [network IP Address]) | "Service: Any" | "Action: Allow" . This allows external access to "NO-SNAT" internal networks via static routes while preventing external access by to "SNAT inter network" via internal networks via static routes.

  • VMware Integrated OpenStack dashboard (Horizon) throws a 504 Gateway Timeout.
    After approximately 1500 networks have been configured, clicking Networks in the dashboard navigation panel might result in a 504 error.

  • Adding new tenant logical router to shared Edge breaks static route.
    When a static route is added to a shared Edge VM for one router, there is no check for a conflict on the shared Edge VM on another router. This issue is fixed for version 2.0. but not this patch.

  • vSphere Datacenter Names with Commas Prevent Deployment.
    If the VMware vSphere Datacenter name has a comma in it (for example: "Palo Alto, CA"), you will be unable to deploy VMware Integrated OpenStack. The deployment wizard displays an invalid parameter error.

    Workaround: If possible modify datacenter names to be used for VMware Integrated OpenStack deployments to omit the "," character.

  • Cluster with NSX-V fails to deploy due to "$" character in password.
    VMware Integrated OpenStack does not properly escape the "$" character when it is used in NSX-V passwords.

    Workaround: If possible modify the NSX-V password to omit the "$" character.

  • Need to run vioconfig start command if any OpenStack node is restarted
    If some of the node VMs in a cluster are restarted, you might need to restart the other nodes also. You can restart each node individually in the vSphere Web Client or by using the sudo vioconfig start command. If you cannot restart any of the nodes, ensure that the VMware Integrated OpenStack manager is running. Restart the manager first, then run sudo vioconfig start command to ensure all the OpenStack nodes start also.

  • After rebooting the Compute Controller, the other services don't start.
    When the VIO-Controller starts, all the services should automatically start.

    Workaround: Before running vioconfig start to reboot the Compute Controller, manually restart the database on the database node.

    In the alternative, perform the following procedure.

    1. Run sudo mysqld_safe --wsrep-recover command on each of the database nodes.

    2. Register the output of the above command. One of the lines will read: Recovered position 5b821365-fafb-11e4-a3d3-471472ccc7b3:38719. Note the value that follows the colon. One of the nodes should return a number higher than the other node.

    3. Choose the database VM where the above number is greatest. If that number is equal on all nodes, choose database01 VM (the first one).

    4. Run sudo service mysql start --wsrep-new-cluster on the selected node.

    5. Run sudo service mysql start on the rest of the database nodes.

    6. Manually restart the remaining OpenStack nodes.

  • "Nova boot image" fails intermittently.
    If the OpenStack Manager IP address is changed (for example, by modifying the FQDN setting), thus causing the OpenStack VMs to fall out of synchronization with the OpenStack Management Service. This bug is fast-tracked for correction.

    Workaround: Manually modify the OpenStack Manager IP address.

    1. From the vSphere Web interface, choose VMware Integrated OpenStack vApp Get Started->Edit Settings...->Networking Properties.

    2. Change the Management Server Network IP Address to the new one.

    3. Power off and restart the VMware Integrated OpenStack vApp.

    4. Using SSH, log in to Management Server console.

    5. Navigate to the /etc/network/interfaces file and edit the IP address setting to the new one.

    6. Restart the OpenStack VMs.

  • HA event can cause OpenStack to restart VMs on another host.
    This is caused by an OpenStack issue (https://bugs.launchpad.net/nova/+bug/1403856). OpenStack performs a periodic power state check on the OpenStack VMs. If it finds a VM powered off, it might treat it like a HA event even though it may about to restart on the same host.

    Workaround: Suspend the periodic check that OpenStack performs. Modify the sync_power_state_interval setting value to -1. This check is desirable. Please review the OpenStack issue above for possible ramifications for your deployment.