We are having an issue with our nexus instance failing to find, both public and private, ruby gems.
(NOTE: I’ll be using one of our private gems as an example, but this issue is not limited to this gem in particular, but also to our other private gems as well as public gems; the issue does not seem to be gem specific.)
When we run a bundle install
using our nexus instance as a source
, bundler returns the following:
Resolving dependencies…
Your bundle is locked to didja_rails_dev (1.0.4) from rubygems repository https://nexus.example.com/repository/rubygems/ or installed locally, but that version can no longer be found in that source.
That means the author of didja_rails_dev (1.0.4) has removed it. You’ll need to update your bundle to a version other than didja_rails_dev (1.0.4) that hasn’t been removed in order to install.
However, we can see the presence of the gem and version when browsing the nexus UI.
We can recreate the error by running gem install didja_rails_dev -v 1.0.4 --source https://nexus.example.com/repository/rubygems/
When trying to update the gem directly with bundle update btv_rails --conservative
we get the following error:
Could not find gem ‘didja_rails_dev (= 1.0.4)’ in rubygems repository https://nexus.example.com/repository/rubygems/, https://rubygems.org/ or installed locally.
The source contains the following gems matching ‘didja_rails_dev’:
- didja_rails_dev-1.0.1
- didja_rails_dev-1.0.2
- didja_rails_dev-1.0.3
So its saying that particular gem version is not in nexus, but again we can see it when browsing the UI.
This also happens with public gems that are cached in nexus, and again we can see its presence in the nexus UI. However, we can get these public gems installed by specifying https://rubygems.org
as an additional source
.
There is nothing in the nexus logs to indicate what the issue might be.
We’ve tried eliminating negative caching, flushing the cache and reindexing.
The issue seems to have started in the last couple of months with version OSS 3.53.0-01
.
Thanks in advance!