Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

, March 6, 2016 at 11:27 PM > To: OpenStack List <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Neutron][tempest] Timestamp service > extension breaks CI > > Keep in mind that fix for ML2 is the correct behavior, not a workaround. > It was not including ext

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

>> >> From: Kevin Benton <ke...@benton.pub> >> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> >> Date: Monday, March 7, 2016 at 11:45 AM >> >> To: OpenStack List <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev]

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

penstack-dev@lists.openstack.org> > Date: Monday, March 7, 2016 at 11:45 AM > > To: OpenStack List <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Neutron][tempest] Timestamp service > extension breaks CI > > But that's the whole point of doing th

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

ilto:openstack-dev@lists.openstack.org>> Date: Monday, March 7, 2016 at 11:45 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI But that's the whole poin

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

>> ML2 - https://review.openstack.org/#/c/276219/ >> *OVN - https://review.openstack.org/#/c/277844/ >> <https://review.openstack.org/#/c/277844/>* >> >> Thanks >> Gary >> >> From: Gary Kotton <gkot...@vmware.com> >> Reply-To: Op

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

nstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI Right, it can't be done in the base right now because core plugins make DB changes after the base plugin has been called. These changes include the initial create proces

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

.@benton.pub> > Reply-To: OpenStack List <openstack-dev@lists.openstack.org> > Date: Sunday, March 6, 2016 at 11:27 PM > To: OpenStack List <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Neutron][tempest] Timestamp service > extension

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

ts.openstack.org>> Subject: Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI Keep in mind that fix for ML2 is the correct behavior, not a workaround. It was not including extension data in create calls so there was an API difference between a create and a get

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

tps://review.openstack.org/#/c/277844/>* Thanks Gary From: Gary Kotton <gkot...@vmware.com> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> Date: Sunday, March 6, 2016 at 4:04 PM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [Neutron][tempest] Tim

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

On 6 March 2016 at 06:04, Gary Kotton wrote: > Hi, > The commit > https://review.openstack.org/#q,4c2c983618ddb7a528c9005b0d7aaf5322bd198d,n,z > causes > the CI to fail. This is due to the fact that the port creation does not > return the created_at and updated_at keys. The

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

ck.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI Hi, The commit https://review.openstack.org/#q,4c2c983618ddb7a528c9005b0d7aaf5322bd198d,n,z causes the CI to fail. This is due to the fact that the port crea

[openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Hi, The commit https://review.openstack.org/#q,4c2c983618ddb7a528c9005b0d7aaf5322bd198d,n,z causes the CI to fail. This is due to the fact that the port creation does not return the created_at and updated_at keys. The tempest test that the keys are the same. Please see [I] I posted patch