Current Series Release Notes¶

5.0.1-37¶

Added is_filter to the remaining scalar attributes in the agent API definition (created_at, started_at, heartbeat_timestamp, and configurations). Some attributes already had is_filter, but these four did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the id and tenant_id attributes in the auto allocated topology API definition. Previously, these attributes were not declared as filterable, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to all scalar attributes in the BGPVPN API definition (id, tenant_id, name, and type). Previously, no BGPVPN attribute was declared as filterable, which caused list operations with query filters (e.g. ?name=foo) to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the metainfo attribute in the service profiles API definition. Other service_profiles attributes already declared is_filter, but metainfo did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to all scalar attributes in the floating IP pools API definition (subnet_id, subnet_name, network_id, cidr, and project_id). Previously, no floating IP pool attribute was declared as filterable, which caused list operations with query filters (e.g. ?subnet_name=foo) to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the remaining scalar attributes in the L3 NDP proxy API definition (id, project_id, router_id, port_id, ip_address, and description). The name attribute already declared is_filter, but the others did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the type attribute in the loggable resources API definition. All logs attributes already declared is_filter, but type on loggable_resources did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the tenant_id attribute in the metering label rules API definition. The metering_labels resource already declared all attributes as filterable, but tenant_id on metering_label_rules did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the remaining scalar attributes in the network IP availability API definition (total_ips, used_ips, and subnet_ip_availability). Some attributes already had is_filter, but these three did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the remaining scalar attributes in the network segment range API definition (default, shared, minimum, maximum, used, and available). Some attributes already had is_filter, but these six did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the rules attribute in the QoS policies API definition and to the type attribute in the rule types API definition. Other QoS attributes already declared is_filter, but these two did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to the segmentation_id attribute in the segment API definition. Other segments attributes already declared is_filter, but segmentation_id did not, which caused list operations with query filters to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to all scalar attributes in the service type API definition (service_type, name, and default). Previously, no service provider attribute was declared as filterable, which caused list operations with query filters (e.g. ?name=foo) to return HTTP 400 when the filter-validation extension is enabled.

Added is_filter to all scalar DB-backed attributes in the TaaS API definitions (tap_services, tap_flows, tap_mirrors, and the taas-vlan-filter extension). Previously, no TaaS attribute was declared as filterable, which caused list operations with query filters (e.g. ?name=foo) to return HTTP 400. This also broke openstack tap service show <name>, openstack tap flow show <name>, and openstack tap mirror show <name> because the client falls back to filtering by name when the initial UUID-based lookup returns 404.