[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946711#comment-14946711
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8940:
--------------------------------------------

GitHub user kansal opened a pull request:

    https://github.com/apache/cloudstack/pull/916

    CLOUDSTACK-8940: Wrong value is inserted into nics table netmask fiel…

    …d when creating a VM - Fixed
    
    Problem: When creating a VM in shared network with no service, the value of 
netmask is added in the table in the CIDR format unlike other cases where it is 
added as normal string in the format xxx.xxx.xxx.xxx. The netmask column in the 
nics table has a length of 15 chars which gets violated if the CIDR exceeds 
it(Max CIDR length can be 18). 
    
    Fix: Before storing the netmask convert from CIDR to native format. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kansal/cloudstack CLOUDSTACK-8940

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/916.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 #916
    
----
commit eb217fab5ef3f210cca1823adbd803568302fa30
Author: Kshitij Kansal <[email protected]>
Date:   2015-10-07T11:33:00Z

    CLOUDSTACK-8940: Wrong value is inserted into nics table netmask field when 
creating a VM - Fixed

----


> Wrong value is inserted into nics table netmask field when creating a VM
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8940
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8940
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Kshitij Kansal
>            Priority: Critical
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to