Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

How to override tempest tests in neutron or networking-ovn repo? Thanks Anil On Mon, Apr 9, 2018 at 8:26 PM, Lucas Alvares Gomes wrote: > Hi, > > > Another idea is to modify test that it will: > > 1. Check how many ports are in tenant, > > 2. Set quota to actual number

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, > Another idea is to modify test that it will: > 1. Check how many ports are in tenant, > 2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is > now, > 3. Try to add 2 ports - exactly as it is now, > > I think that this should be still backend agnostic and should fix

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

t; *To: *OpenStack List <openstack-dev@lists.openstack.org> > *Subject: *Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario > tests and OVN metadata > > > > this issue isn't only for networking ovn, please note that it happens with > a flew other vendor plugi

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

8 at 8:56 AM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata this issue isn't only for networking ovn, please note that it happens with a flew other vendor plugins (like nsx), at least this is somet

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

this issue isn't only for networking ovn, please note that it happens with a flew other vendor plugins (like nsx), at least this is something we have found in downstream certifications. Cheers, On Sat, Apr 7, 2018, 12:36 AM Daniel Alvarez wrote: > > > > On 6 Apr 2018, at

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

> On 6 Apr 2018, at 19:04, Sławek Kapłoński wrote: > > Hi, > > Another idea is to modify test that it will: > 1. Check how many ports are in tenant, > 2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is > now, > 3. Try to add 2 ports - exactly as

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

> On 6 Apr 2018, at 19:04, Sławek Kapłoński wrote: > > Hi, > > Another idea is to modify test that it will: > 1. Check how many ports are in tenant, > 2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is > now, > 3. Try to add 2 ports - exactly as

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, Another idea is to modify test that it will: 1. Check how many ports are in tenant, 2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is now, 3. Try to add 2 ports - exactly as it is now, I think that this should be still backend agnostic and should fix this problem. >

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, I don’t know how networking-ovn is working but I have one question. > Wiadomość napisana przez Daniel Alvarez Sanchez w dniu > 06.04.2018, o godz. 15:30: > > Hi, > > Thanks Lucas for writing this down. > > On Thu, Apr 5, 2018 at 11:35 AM, Lucas Alvares Gomes

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, Thanks Lucas for writing this down. On Thu, Apr 5, 2018 at 11:35 AM, Lucas Alvares Gomes wrote: > Hi, > > The tests below are failing in the tempest API / Scenario job that > runs in the networking-ovn gate (non-voting): > >

[openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, The tests below are failing in the tempest API / Scenario job that runs in the networking-ovn gate (non-voting): neutron_tempest_plugin.api.admin.test_quotas_negative.QuotasAdminNegativeTestJSON.test_create_port_when_quotas_is_full