[
https://issues.apache.org/jira/browse/CLOUDSTACK-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946316#comment-13946316
]
Nux commented on CLOUDSTACK-6240:
---------------------------------
Thanks Jayapal, this one applied cleanly.
https://reviews.apache.org/r/19351/diff/2/raw/
> ipset requires VM stop/start to get updated
> -------------------------------------------
>
> Key: CLOUDSTACK-6240
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6240
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Network Controller, XenServer
> Affects Versions: 4.2.1, 4.3.0, 4.4.0
> Environment: CentOS 6.5 64bit
> Reporter: Nux
> Assignee: Jayapal Reddy
> Labels: ipset, security_groups
> Attachments:
> 0001-CLOUDSTACK-6240-Fixed-updating-advanced-SG-rules-for-master.patch,
> 0001-CLOUDSTACK-6240-Fixed-updating-advanced-SG-rules-for.patch
>
>
> In an advanced zone with security groups, when a new IP address is acquired
> for a VM, this IP is not added in the running ipset corresponding to the VM.
> `ipset -L` continues to only show the main IP until the VM is restarted.
> Adding the extra IP is as easy as:
> ipset add i-2-3-VM 10.187.72.214
--
This message was sent by Atlassian JIRA
(v6.2#6252)
