yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57268
[Bug 1629368] Re: Assert fails if Subnet has extra fields
I don't think it's neutron issue to solve.
Also, please add details about tempest failure you see. It's not clear
where you hit it.
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1629368
Title:
Assert fails if Subnet has extra fields
Status in tempest:
New
Bug description:
Why assertion checks are done in such a way that if a subnet has
couple more fields other that {u'name', u'enable_dhcp', u'network_id',
u'tenant_id', u'dns_nameservers' , u'ipv6_ra_mode',
u'allocation_pools',u'gateway_ip', u'ipv6_address_mode',
u'ip_version', u'host_routes', u'cidr', u'id', u'subnetpool_id'} the
assertions fails ?
The tests should check all these fields are present and it should just
pass regrdless is that subnet has more fields.
for ex: subnet-show outputs:
assertion between [1] and [2] should pass.
[1]
{u'name': u'', u'enable_dhcp': True, u'network_id': u'047e846a-abb9-4174-a9f7-daef5c125003', u'tenant_id': u'14793945c3674cd28f6b795c991c6091', u'dns_nameservers': [], u'ipv6_ra_mode': None, u'allocation_pools': [{u'start': u'10.100.0.2', u'end': u'10.100.0.14'}], u'gateway_ip': u'10.100.0.1', u'ipv6_address_mode': None, u'ip_version': 4, u'host_routes': [], u'cidr': u'10.100.0.0/28', u'id': u'f9747d21-e2c7-417b-aab8-ad32e2322c56', u'subnetpool_id': None}
[2]
{u'name': u'', u'enable_dhcp': True, u'network_id': u'047e846a-abb9-4174-a9f7-daef5c125003', u'tenant_id': u'14793945c3674cd28f6b795c991c6091', u'dns_nameservers': [], u'ipv6_ra_mode': None, u'allocation_pools': [{u'start': u'10.100.0.2', u'end': u'10.100.0.14'}], u'gateway_ip': u'10.100.0.1', u'ipv6_address_mode': None, u'ip_version': 4, u'host_routes': [], u'cidr': u'10.100.0.0/28', u'id': u'f9747d21-e2c7-417b-aab8-ad32e2322c56', u'subnetpool_id': None,
u'XYZ: u`ABC...etc}
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/tempest/+bug/1629368/+subscriptions
References