IssueTracker

I'm seeing the same passing any filter expression for aggregatedList

I'm seeing this issue as well when attempting to filter an aggregatedList for compute backend services.

API error: "googleapi: Error 400: Invalid value for field 'filter': 'name = my-backend-service'. Invalid list filter expression., invalid"

Here's the JSON response when I attempt to use this feature via curl: https://paste.googleplex.com/6197368772886528
I know the backend service exists due to it showing up when I don't use the filter query param: https://paste.googleplex.com/5149442621571072

+1 I'm seeing this issue as well for querying on name.

I have this problem too, with filtering on aggregateList if disks.  

Noted that:

curl 'https://www.googleapis.com/compute/v1/projects/my-project/aggregated/disks?alt=json&filter=labels.snaps+eq+daily'
=> returns expected filtered results

[EDIT: silly example deleted.  The point was that the google-api-python-client library produces a request that 400's, but that the request above actually does work]

+1 - This is an issue for SAP deployment automation.

Just came across this issue as well. Is there an ETA on a fix?

Interestingly, it works when you use a string formatted as the gcloud cli client.

For example (pseudocode):
regex_excaped_string = "name eq \"name\\-of\\-instance\""
instances.aggregatedList("project_id", format=regex_escaped_string)

+1

I can't get https://cloud.google.com/compute/docs/reference/rest/v1/instanceTemplates/list to work either.

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "invalid",
    "message": "Invalid value for field 'filter': 'labels.foobar = true'. Invalid list filter expression."
   }
  ],
  "code": 400,
  "message": "Invalid value for field 'filter': 'labels.foobar = true'. Invalid list filter expression."
 }
}

I have this too when trying to filter firewall rules sourceRanges. Any news on this it's been open for 5 months ?

The gcloud command works using

    gcloud compute firewall-rules list --filter="sourceRanges:(0.0.0.0/0)"

However putting the same filter into the api, I get

    Invalid value for field 'filter': 'sourceRanges:(0.0.0.0/0)'. Invalid list filter expression

Is there another way of specifying list values in the API ? I see this is a P2 but really needs bumping up as i'm blocked on a client project

Looks a lot like previously seen issues.

I am seeing the same thing for "compute.snapshots.list", should I open a separate issue for that? This is happening when I try to compare the time stamp. For example using the filter to search for a name works:

> export PROJECT=$(gcloud config get-value project)
> curl -H "$(oauth2l header cloud-platform)" \
-H "Content-Type: application/json" \
https://www.googleapis.com/compute/v1/projects/${PROJECT}/global/snapshots\?filter\=name%3A%22utilities-vm-\*%22
{
 "kind": "compute#snapshotList",
 "id": "projects/xxxx/global/snapshots",
 "items": [
  {
   "kind": "compute#snapshot",
   "id": "206264346296184964",
   "creationTimestamp": "2019-02-11T20:41:15.991-08:00",
   "name": "utilities-vm-2019-02-11",
   "status": "READY",

Here is the one that fails:

> curl -H "$(oauth2l header cloud-platform)" \
-H "Content-Type: application/json" \
https://www.googleapis.com/compute/v1/projects/${PROJECT}/global/snapshots\?filter\=creationTimestamp%3E%2220190219%22
{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "invalid",
    "message": "Invalid value for field 'filter': 'creationTimestamp\u003e\"20190219\"'. Invalid list filter expression.",

And with gcloud it works fine:

> gcloud compute snapshots list --filter 'creationTimestamp>2019-02-11'
NAME                     DISK_SIZE_GB  SRC_DISK                       STATUS
utilities-vm-2019-02-11  20            us-east4-c/disks/utilities-vm  READY

I am seeing the same issue w/ the java client. In kotlin:
"(creationTimestamp < ${ZonedDateTime.now(ZoneOffset.UTC)
                                    .minusHours(numHoursPrevious)
                                    .format(dateTimeFormatter)})" is my filter and I get:

com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
{
  "code" : 400,
  "errors" : [ {
    "domain" : "global",
    "message" : "Invalid value for field 'filter': '(creationTimestamp > 2019-05-01T06:29:46.613)'. Invalid list filter expression.",
    "reason" : "invalid"
  } ],
  "message" : "Invalid value for field 'filter': '(creationTimestamp > 2019-05-01T06:29:46.613)'. Invalid list filter expression."
}

The same filter works w/ gcloud command line tool.

Edit: If you escape the timestamp like so:
"(creationTimestamp < \"${ZonedDateTime.now(ZoneOffset.UTC)
                                    .minusHours(numHoursPrevious)
                                    .format(dateTimeFormatter)}\")"

it works. These escaped quotes are not intuitive nor documented. Additionally piping more filters using parenthesis does not work as expected unless an AND is used explicitly.

https://developers.google.com/apis-explorer/#p/compute/v1/compute.snapshots.list?project=cc-iops-dev&filter=creationTimestamp%253E%25222019-05-01T21%253A04%253A58.752%2522&_h=110& is another example using the api explorer. If you change the > sign in the filter to an = or != you get a 200 response. It seems > and < are causing problems for filters. I see this in snapshot.list, instances.list, and more.

I should note that the issue with the filter in instances.aggregatedList method is fixed now. If you get similar issues while using other methods, it is recommended to raise another ticket to be investigated.

In response to #16, I created a public issue to investigate it. You can keep track of it in the following link[1].
If you want to subscribe to receive notifications about its progress, you can star that issue.

[1]: https://issuetracker.google.com/132676194

🤖 This is an automatic update. The status of the related internal issue(s) listed in "Blocked By" has changed, so we've done the following:

* Moved this issue to a locked sub-component, because the issue has been closed. Please open a new issue if you need Google to re-visit this topic.

You can read more about what these statuses mean at https://developers.google.com/issue-tracker/concepts/issues#fields