[
https://issues.apache.org/jira/browse/CLOUDSTACK-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945246#comment-13945246
]
Nux commented on CLOUDSTACK-6240:
---------------------------------
Jayapal,
Any chance you can provide a working patch for 4.3?
patch -p1 < ipset.patch
patching file
api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java
Hunk #1 succeeded at 118 with fuzz 1 (offset 26 lines).
Hunk #2 succeeded at 170 with fuzz 1 (offset 28 lines).
patching file
api/src/org/apache/cloudstack/api/command/user/vm/RemoveIpFromVmNicCmd.java
Hunk #1 succeeded at 129 (offset -2 lines).
Hunk #2 succeeded at 145 with fuzz 1 (offset -2 lines).
patching file
server/src/com/cloud/network/security/SecurityGroupManagerImpl.java
Hunk #1 FAILED at 1350.
1 out of 1 hunk FAILED -- saving rejects to file
server/src/com/cloud/network/security/SecurityGroupManagerImpl.java.rej
> 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)
