[
https://issues.apache.org/jira/browse/CLOUDSTACK-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882008#comment-15882008
]
ASF GitHub Bot commented on CLOUDSTACK-9638:
--------------------------------------------
GitHub user bvbharatk opened a pull request:
https://github.com/apache/cloudstack/pull/1967
CLOUDSTACK-9638 Problems caused when inputting double-byte numbers fo…
…r custom compute offerings
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bvbharatk/cloudstack CLOUDSTACK-9638
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1967.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 #1967
----
commit 59312dd976a6fb5e4d5d3a5b701fc1cccac9a3d2
Author: Bharat Kumar <[email protected]>
Date: 2017-01-03T12:25:08Z
CLOUDSTACK-9638 Problems caused when inputting double-byte numbers for
custom compute offerings
----
> Problems caused when inputting double-byte numbers for custom compute
> offerings
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9638
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9638
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.9.0
> Reporter: Bharat Kumar
> Assignee: Bharat Kumar
> Fix For: 4.9.1.0
>
>
> When creating a VM with a custom compute offering, CloudPlatform allows the
> input of double-byte numbers. The VM will be created but listVirtualMachines
> will subsequently fail with an exception. The problem seems to be with the
> value of detail_value for the associated entry in the user_vm_view table. If
> you manually change it to a regular number the issue is resolved. Double-byte
> numbers should either be considered invalid for custom offerings and
> rejected, or listVMs should work when they are used for a VM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
