You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/04/25 03:13:39 UTC

[jira] [Commented] (CLOUDSTACK-4611) [Ubuntu] ebtables-save command not exist on Ubuntu 12.04

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

ASF subversion and git services commented on CLOUDSTACK-4611:
-------------------------------------------------------------

Commit d66677101c7770b5c4b8c39064eba5ee94d124c6 in cloudstack's branch refs/heads/4.5 from [~rohit.yadav@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d666771 ]

CLOUDSTACK-4611: cleanup_rules using ebtables rules from /proc/modules

The SG python script depends on ebtables-save which is not available on Debian
based distros (Ubuntu and Debian for example). The commit uses /proc/modules
to find available bridge tables (one of nat, filter or broute) and then
find VMs that need to be removed. Further it uses set() to remove duplicate VMs
so we don't try to remove a VM's rules more than once leading to unwanted errors
in the log.

Signed-off-by: Rohit Yadav <ro...@shapeblue.com>


> [Ubuntu] ebtables-save command not exist on Ubuntu 12.04
> --------------------------------------------------------
>
>                 Key: CLOUDSTACK-4611
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4611
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Wei Zhou
>            Assignee: Rohit Yadav
>            Priority: Minor
>             Fix For: 4.6.0, 4.5.1
>
>
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py use ebtables-save in cleanup_rules().
> However, ebtables-save command exists on CentOS/RHEL, but not exist on Ubuntu 12.04



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