Issue with Nexus Not Going Upstream for Docker Image with Same Tag After Cache Invalidation

Sonatype Nexus Repository
, , ,
1

I have a Nexus setup with three repositories: two proxy repositories and one grouped repository. All repositories have their metadata and content max-age set to -1. However, after invalidating the cache for the grouped repository, Nexus is still not going upstream to fetch a new image with the same tag, when I updated the docker image on the upstream,
used cache invalidate opt, and used api too,
Observed that , when invalidated cache on grouped nexus, it is updating for subsequent members on group also, from the logs.

This is going upstream when deleting docker image on one of its members where it is actually have.

Has anyone encountered this issue? What could be the cause of Nexus not fetching the latest image from the upstream repository despite cache invalidation?

2

If you haven’t already, there should be an outbound request log which might contain information.

3

where can I find this information, I cannot see anywhere, I am working work only 1 repo, and in 2nd repo, I am getting the issue

4

The nexus log folder should have an outbound-request.log or similarly named file