GitHub user sureshanaparti opened a pull request:
https://github.com/apache/cloudstack/pull/1891
CLOUDSTACK-9730: [VMware] Unable to add a host with space in its name to
existing VMware cluster
Issue: Unable to add a host with space in its name to existing VMware
cluster
Root Cause: Previously cluster url from API used to be inserted into DB
after validation of inventory url. White spaces in url would be encoded as '+'
during creation of URI object which are being inserted into database. Further
references of the cluster's data center name would see '+' symbols instead of
white space which is incorrect.
Fix: Skip update of encoded cluster url path in cluster_details table while
adding host to existing cluster.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9730
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1891.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1891
----
commit 9b5b3aa30a04589be843c66dd8173a2b94a92d4d
Author: Suresh Kumar Anaparti <suresh.anapa...@accelerite.com>
Date: 2017-01-05T23:12:14Z
CLOUDSTACK-9730: [VMware] Unable to add a host with space in its name to
Cluster
Skip update of encoded cluster url path in cluster_details table while
adding host to existing cluster.
Previously cluster url from API used to be inserted into DB after
validation of inventory url. White spaces in url would be encoded as '+' during
creation of URI object which are being inserted into database. Further
references of the cluster's data center name would see '+' symbols instead of
white space which is incorrect.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
