Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 23 Dec 2014 10:16:13 +0000 (UTC)
From: "Daan Hoogland (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12710124.1398280973000.90295.1419329773592@Atlassian.JIRA>
In-Reply-To: <JIRA.12710124.1398280973000@Atlassian.JIRA>
References: <JIRA.12710124.1398280973000@Atlassian.JIRA>
 <JIRA.12710124.1398280973413@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-6485) [vpc] new private gateway
 network is registered wrong in network table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6485?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daan Hoogland updated CLOUDSTACK-6485:
--------------------------------------
    Fix Version/s:     (was: 4.6.0)

> [vpc] new private gateway network is registered wrong in network table
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6485
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-648=
5
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Virtual Router
>    Affects Versions: 4.2.1, 4.3.0, 4.4.0, 4.3.1
>            Reporter: Anton Opgenoort
>            Assignee: Daan Hoogland
>
> When creating a private gateway for a VPC router on a network not yet kno=
wn to Cloudstack, Cloudstack =E2=80=98documents=E2=80=99 this network in th=
e networks table.
> For normal guest networks, which should be associated with a single VPC, =
Cloudstack includes the VPC_ID in the database. The VPC_ID field is used to=
 provision all networks and nics on a VPC router when it is created. Since =
this table is all about network provisioning it makes sense to =E2=80=98doc=
ument=E2=80=99 the network cidr and gateway present in that nework. For gue=
st tiers this usually is the VPC router itself, so the interface IP=E2=80=
=99s on a VPC router are the gateway IP=E2=80=99s found in the networks tab=
le.
> Unfortunately the VPC_ID is also recorded for the private gateway network=
 when it is first created. So the first VPC to be plugged on the private ga=
teway network also has that same network associated as a guest network tier=
, instead of just a private gateway network.
> This by itself will not quickly become a problem, because private gateway=
s are first plugged on a running vpc router which is not likely to be recre=
ated any time soon after that.
> But as soon as this first ever VPC router on the private gateway network =
is recreated due to a destroy of the VPC Router, all associated networks ar=
e looked up in the networks table.=20
> Because the private gateway network is =E2=80=98documented=E2=80=99 with =
the actual upstream gateway used by the VPC router defintion, the VPC route=
r provisions a NIC on the private gateway network using the IP address of t=
he actual upstream gateway creating an IP conflict on the private gateway n=
etwork, effectively breaking down the upstream gateway functionality for al=
l attached private gateways of other vpc's.


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