>
> As a work around we reread the object when we need to process the rules.
> Not sure if anyone else has hit this
>
> Thanks
>
> Gary
>
>
>
> *From: *Kevin Benton <ke...@benton.pub>
> *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
>
stack-dev@lists.openstack.org>
Date: Monday, June 19, 2017 at 10:01 AM
To: OpenStack List <openstack-dev@lists.openstack.org>
Cc: "isaku.yamah...@gmail.com" <isaku.yamah...@gmail.com>
Subject: Re: [openstack-dev] [neutron] security group OVO change
Do you mean the callback event for
Do you mean the callback event for AFTER_CREATE is missing the rules when
it's for default security groups?
On Sun, Jun 18, 2017 at 4:44 AM, Gary Kotton wrote:
> Hi,
> That patch looks good. We still have an issue in that the create security
> groups does not return the list
Hi,
That patch looks good. We still have an issue in that the create security
groups does not return the list of the default rules.
Thanks
Gary
On 6/17/17, 2:33 AM, "Isaku Yamahata" wrote:
It also broke networking-odl.
The patch[1] is needed to unbreak.
It also broke networking-odl.
The patch[1] is needed to unbreak.
[1] https://review.openstack.org/#/c/448420/
necessary db info is taken from context.session.new.
But with OVO, those expunge themselves with create method.
Those info needs to be passed as callback argument.
Thanks,
On Fri, Jun
To close the loop here,
- this also broke heat py3 job (https://launchpad.net/bugs/1698355)
- we polished https://review.openstack.org/474575 to fix both
vmware-nsx and heat issues
- I also posted a patch for oslo.serialization for the bug that
triggered MemoryError in heat gate:
Hi,
The commit https://review.openstack.org/284738 has broken decomposed plugins
(those that extend security groups and rules). The reason for this is that
there is a extend callback that we use which expects to get a database object
and the aforementioned patch passes a new neutron object.
I