Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: unknown (athena.apache.org: error in processing during lookup of
 pdion@cloudops.com)
MIME-Version: 1.0
In-Reply-To: 
 <CAP997Uf7xme9h8FA8kkrYdMaJ1Oa8P67YQUL0hJ8krxQWzFX8g@mail.gmail.com>
References: 
 <CAP997Uf7xme9h8FA8kkrYdMaJ1Oa8P67YQUL0hJ8krxQWzFX8g@mail.gmail.com>
Date: Thu, 13 Nov 2014 12:15:51 -0500
Message-ID: 
 <CAD97ioes+6vn1Zu11F6ip1j_v3San2B-cebaDb9P-Vb85FnuMw@mail.gmail.com>
Subject: Re: [ACS430] Instances / network unable to access external network
 until an egress rule has been applied
From: Pierre-Luc Dion <pdion@cloudops.com>
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a113fddfa06f6d00507c0aabe

--001a113fddfa06f6d00507c0aabe
Content-Type: text/plain; charset=UTF-8

Hi Erik,

I've experiance similar behavior, but in my case, doing a stop/start from
CloudStack of VR did solve the problem. I'm still not sure if rebooting the
VR via SSH instead of using CloudStack API was root cause of the problem.


*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683

*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_


On Tue, Nov 11, 2014 at 4:54 PM, Erik Weber <terbolous@gmail.com> wrote:

> I'm trying to find out if a bug we experience is known and fixed in a later
> version or not.
>
> We're running ACS/CCP 4.3.0 on XenServer 6.2, with advanced networking
> (VLAN isolated).
>
> The problem is that whenever a network is created or restarted it won't
> allow external access before an egress rule has been applied and deleted
> again.
>
> I suspect this is because of wrong iptables rules being applied on startup,
> and that the rule addition/removal reconfigures it to be correct.
>
> I've done some initial searching in jira, but not found anything.
>
> Has anyone experienced anything like this, or are able to find any
> commits/issues that matches this issue?
>
>
> --
> Erik
>

--001a113fddfa06f6d00507c0aabe--