Segment ignore sorting parameters

Tested and confirmed this bug with system built from master. Requesting sort by descending order:

$ curl -g -s -X GET "http://localhost:9696/v2.0/segments?sort_dir=desc&sort_key=name" -H "Content-type: application/json" -H "X-Auth-Token: $TOKEN" | jq
{
  "segments": [
    {
      "name": "segment1",
      "network_id": "8445c42e-d281-4fd0-8ff0-481f1356bc0b",
      "segmentation_id": 2016,
      "network_type": "vlan",
      "physical_network": "physnet1",
      "id": "44a4ff93-0ab5-4b94-b7ea-b0266d022f8d",
      "description": null
    },
    {
      "name": "segment2",
      "network_id": "8445c42e-d281-4fd0-8ff0-481f1356bc0b",
      "segmentation_id": 2016,
      "network_type": "vlan",
      "physical_network": "physnet2",
      "id": "ae421d4d-4b76-4e1a-bb70-f51c46386c2f",
      "description": null
    },
    {
      "name": null,
      "network_id": "96efc697-2aa9-4dbf-b1f5-22234f33cddf",
      "segmentation_id": 1021,
      "network_type": "vxlan",
      "physical_network": null,
      "id": "97258b18-0f90-4c97-90b9-15b25f320908",
      "description": null
    },
    {
      "name": null,
      "network_id": "ba67524e-c8fa-4d9e-b701-2b8cf67617e2",
      "segmentation_id": null,
      "network_type": "flat",
      "physical_network": "public",
      "id": "44a28675-60de-420c-8f3a-5653a7acdedc",
      "description": null
    }
  ]
}

Returns the same as ascending order:

$ curl -g -s -X GET "http://localhost:9696/v2.0/segments?sort_dir=asc&sort_key=name" -H "Content-type: application/json" -H "X-Auth-Token: $TOKEN" | jq
{
  "segments": [
    {
      "name": "segment1",
      "network_id": "8445c42e-d281-4fd0-8ff0-481f1356bc0b",
      "segmentation_id": 2016,
      "network_type": "vlan",
      "physical_network": "physnet1",
      "id": "44a4ff93-0ab5-4b94-b7ea-b0266d022f8d",
      "description": null
    },
    {
      "name": "segment2",
      "network_id": "8445c42e-d281-4fd0-8ff0-481f1356bc0b",
      "segmentation_id": 2016,
      "network_type": "vlan",
      "physical_network": "physnet2",
      "id": "ae421d4d-4b76-4e1a-bb70-f51c46386c2f",
      "description": null
    },
    {
      "name": null,
      "network_id": "96efc697-2aa9-4dbf-b1f5-22234f33cddf",
      "segmentation_id": 1021,
      "network_type": "vxlan",
      "physical_network": null,
      "id": "97258b18-0f90-4c97-90b9-15b25f320908",
      "description": null
    },
    {
      "name": null,
      "network_id": "ba67524e-c8fa-4d9e-b701-2b8cf67617e2",
      "segmentation_id": null,
      "network_type": "flat",
      "physical_network": "public",
      "id": "44a28675-60de-420c-8f3a-5653a7acdedc",
      "description": null
    }
  ]
}

While the sorting extension is enabled:

$ neutron ext-list | grep sorting
| sorting | Sorting support

Fix proposed to branch: master
Review: https://review.openstack.org/561361

Reviewed: https://review.openstack.org/561361
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=43d451d86f8c1f9dff2a8580089a631680bb0c09
Submitter: Zuul
Branch: master

commit 43d451d86f8c1f9dff2a8580089a631680bb0c09
Author: Hongbin Lu <email address hidden>
Date: Fri Apr 13 21:47:02 2018 +0000

    Enable sorting and pagination for segments

    It looks the sorting and pagination are natively supported in
    segment db layer but the segment controller doesn't mark these
    features as supported. This patch fixes it.

    Change-Id: I325396bb0256196ee6c6fc42cc812a0c75ae3827
    Closes-Bug: #1763161

This issue was fixed in the openstack/neutron 13.0.0.0b2 development milestone.