Public bug reported: Recently we added the server list query param validation in json schema. In schema, 'accessIPv4' and 'accessIPv6' are allowed which does not match with what DB has. It is 'access_ip_v4' and 'access_ip_v6' in DB.
Below schema should be fixed accordingly to allow the 'access_ip_v4' and 'access_ip_v6' as valid filter. https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/servers.py#L343-L344 On other note: 'accessIPv4' and 'accessIPv6' are the something API accept and return and internally API layer translate those param to their respective field('access_ip_v4' and 'access_ip_v6') present in DB. So user does not know anything about 'access_ip_v4' and 'access_ip_v6'. They are not in API representation actually. List filter and sort param should be same as field return in GET or accepted in POST/PUT which are 'accessIPv4' and 'accessIPv6'. But that is something new attribute support in filter and can be done later after discussion. ** Affects: nova Importance: Undecided Assignee: Ghanshyam Mann (ghanshyammann) Status: New ** Changed in: nova Assignee: (unassigned) => Ghanshyam Mann (ghanshyammann) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1661195 Title: Servers filter by access_ip_v4 does not filter servers Status in OpenStack Compute (nova): New Bug description: Recently we added the server list query param validation in json schema. In schema, 'accessIPv4' and 'accessIPv6' are allowed which does not match with what DB has. It is 'access_ip_v4' and 'access_ip_v6' in DB. Below schema should be fixed accordingly to allow the 'access_ip_v4' and 'access_ip_v6' as valid filter. https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/servers.py#L343-L344 On other note: 'accessIPv4' and 'accessIPv6' are the something API accept and return and internally API layer translate those param to their respective field('access_ip_v4' and 'access_ip_v6') present in DB. So user does not know anything about 'access_ip_v4' and 'access_ip_v6'. They are not in API representation actually. List filter and sort param should be same as field return in GET or accepted in POST/PUT which are 'accessIPv4' and 'accessIPv6'. But that is something new attribute support in filter and can be done later after discussion. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1661195/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
