NXRM 3.13.0 fails to list Blob stores if AWS access/secret key pair is deleted


#1

Hello all,

I’ve been doing some work with Nexus/S3 blob stores and ran into a problem. I successfully connected a Nexus Blob store to an AWS S3 bucket using access/secret key pair. Then, I deleted the key pair. When I refresh the Blob store list, I get a warning from Nexus (naturally) that tells me:


The AWS Access Key Id you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; Request ID: …

I expected something like this…that’s all fine. What I did NOT expect was that:

  • the Blob store I created in Nexus is gone; let’s call it BlobStoreA
  • I can’t create a new Blob store with the same name; even though Nexus doesn’t show BlobStoreA, it seems to still want to connect to it (and the warning about the keys keeps appearing)
  • if I create a new Blob store, IT won’t even show up!

Is there a way to edit knowledge of Blob stores outside the UI? Is this a known bug that is being addressed? Or am I missing something here?

FYI using OSS 3.13.0-01

Thanks,

Ryan


#2

This is a known issue: https://issues.sonatype.org/browse/NEXUS-18254

I believe the fix is going into the upcoming 3.15.0 release.


#3

Great! Thanks for the quick reply.

What’s the ETA for 3.15.0?