Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

uld hit this every time you re-run stack.sh, no? > > > > > >> >> >> *From:* Dan Wendlandt [mailto:d...@nicira.com] >> *Sent:* Wednesday, May 16, 2012 7:55 AM >> *To:* gkot...@redhat.com >> *Cc:* Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

t; *Cc:* Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net <mailto:netstack@lists.launchpad.net> *Subject:* Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue On Wed, May 16, 2012 at 1:43 AM, Gary Kotton mailto:gkot...@redhat.com>> wrote: Th

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

out how I can test the fix with respect to >>> the devstack setup (since this happens only on installation)… >>> >> >> Your explanation makes sense. I think there was a recent comment to >> automatically initialize all networks when nova-network is started, in c

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

> nova-network was started on a new host (e.g., in an HA configuration) or > after a host reboot. Since devstack creates the network using nova-manage > before starting nova-network, this would trigger the behavior your > describe. For more info, see: > https://github.com/openstac

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

> > > ** ** > > *From:* Dan Wendlandt [mailto:d...@nicira.com] > *Sent:* Wednesday, May 16, 2012 7:55 AM > *To:* gkot...@redhat.com > *Cc:* Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net > *Subject:* Re: [Netstack] Fwd: [Openstack] [devstack/quantum] > Conf

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

...@redhat.com Cc: Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net Subject: Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue On Wed, May 16, 2012 at 1:43 AM, Gary Kotton wrote: Thanks! As far as I recall, and I may certain be wrong here, but in the past I did not see

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

On 05/16/2012 05:55 PM, Dan Wendlandt wrote: On Wed, May 16, 2012 at 1:43 AM, Gary Kotton > wrote: Thanks! As far as I recall, and I may certain be wrong here, but in the past I did not see the GW created until the first VM was deployed. Now I am see

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

On Wed, May 16, 2012 at 1:43 AM, Gary Kotton wrote: > ** > Thanks! > As far as I recall, and I may certain be wrong here, but in the past I did > not see the GW created until the first VM was deployed. Now I am seeing the > GW created when the various services are started. > I have noticed this

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

Hi, True, something is fishy. I know for certain that it worked last week Thursday - I tested devstack with Linuxbridge and OVS plugins. Thanks Gary On 05/16/2012 10:54 AM, Sumit Naiksatam (snaiksat) wrote: This is probably not a devstack issue. The problem is with the LB gateway driver wher

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

Thanks! As far as I recall, and I may certain be wrong here, but in the past I did not see the GW created until the first VM was deployed. Now I am seeing the GW created when the various services are started. Thanks Gary On 05/16/2012 10:54 AM, Sumit Naiksatam (snaiksat) wrote: This is proba

Re: [Netstack] Fwd: [Openstack] [devstack/quantum] Configuration issue

This is probably not a devstack issue. The problem is with the LB gateway driver wherein the IP address is trying to be set on a bridge device which already has an IP address. The check for an existing bridge is being performed, but the IP address is being set outside that check. Ideally, this code