Fetching drives results in space image and readme getting lost

[JammingBen]

Describe the bug

Fetching drives via the https://localhost:9200/graph/v1beta1/drives endpoint may result in space image and readme getting lost. This only goes for spaces where the current user is not a member of.

Steps to reproduce

1. As margaret, create a space and upload an image
2. As admin, fetch all spaces via https://localhost:9200/graph/v1beta1/drives (via curl or e.g. by visiting the spaces overview in the admin settings app)
3. As margaret, reload the spaces overview

Expected behavior

The newly created space has the uploaded image.

Actual behavior

The image and description are gone. The https://localhost:9200/graph/v1beta1/drives returns no special property for the newly create space (although the image and the md file are still present on the disc).

[JammingBen]

cc @tbsbdr @dragotin please decide if this is p1 or p2

[kulmann]

I'm really baffled 😅 we tested this on two local machines and the public demo instance and were able to reproduce it 100% of the time.

[micbar]

In both cases, this is a blocker.

[ScharfViktor]

• TODO: add an api test for this case [test-only] test for #452 #826

[ScharfViktor]

@aduffeck You're right. It came back after a while.

[ScharfViktor]

Tested on decomposed, that bug is only with posix.

[aduffeck]

I also see it using the decomposed driver, which makes sense as it's a problem with the cache in the graph API.

Steps to reproduce:

1. Restart server
2. List spaces as admin (which leads to the cache being filled with the empty image attribue)
3. List spaces as margaret -> empty image until the TTL cache expires