[BUG] Inconsistent responses between GET /_snapshot/_status and GET /_snapshot/{repository}/_status

[dblock]

Describe the bug

Coming from opensearch-project/opensearch-api-specification#756 we create a snapshot in my-fs-repository and are seeing the following.

1. GET /_snapshot/_status returns the snapshot.

[INFO] {
  "snapshots": [
    {
      "snapshot": "my-test-snapshot",
      "repository": "my-fs-repository",
      "uuid": "1-K65GWuQmOsGGwfp3oq7A",
      "state": "STARTED",
      "include_global_state": false,
      "shards_stats": {
        "initializing": 0,
        "started": 0,
        "finalizing": 3,
        "done": 1,
        "failed": 0,
        "total": 4
      },
      "stats": {
        ...
  ]
}

2. GET /_snapshot/{repository}/_status immediately after sometimes does not.

[INFO] => GET /_snapshot/my-fs-repository/_status ({}) [application/json] 
[INFO] <= 200 (application/json; charset=UTF-8) | {
  "snapshots": []
}
[INFO] {
  "snapshots": []
}

3. GET /_snapshot/my-fs-repository/my-test-snapshot/_status immediately after returns the data as above.

Related component

Storage:Snapshots

To Reproduce

1. Check out https://github.com/opensearch-project/opensearch-api-specification
2. From tests/snapshot run docker compose up
3. npm run test:spec -- --tests tests/snapshot

Seems to be reproduced 75% of the time in CI.

Expected behavior

Consistent API behavior.

Additional Details

2.18

[Xtansia]

I believe GET /_snapshot/_status and GET /_snapshot/{repository}/_status only return actively running snapshots, where as GET /_snapshot/{repository}/{snapshot}/_status returns the snapshot regardless of status. So I think it might just be that the snapshot completed between request 1. and 2..

[dblock]

That's a strange API :( I think you're right, closing.