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

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

GitHub user remibergsma opened a pull request:

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

    CLOUDSTACK-9256 add unique key for static routes in json

    Static routes that are being set do not show up in the static_routes.json 
file. The reason for this is that the index that is used, is the gateway 
address, which is not unique. Hence stuff is overwritten and lost.
    
    Ping @borisroman @wilderrodrigues @DaanHoogland 

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

    $ git pull https://github.com/remibergsma/cloudstack CLOUDSTACK-9256

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

    https://github.com/apache/cloudstack/pull/1364.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 #1364
    
----
commit 62fc6fef97efb2c938737262cabb9254fca55ba1
Author: Remi Bergsma <[email protected]>
Date:   2016-01-25T16:17:55Z

    CLOUDSTACK-9256 add unique key for static routes in json

----


> Static routes get lost after network restart
> --------------------------------------------
>
>                 Key: CLOUDSTACK-9256
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9256
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.7.0
>            Reporter: Remi Bergsma
>            Assignee: Remi Bergsma
>
> Static routes that are being set do not show up in the static_routes.json 
> file. The reason for this is that the index that is used, is the gateway 
> address, which is not unique. Hence stuff is overwritten and lost.



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

Reply via email to