You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 5.x
Distribution: Ubuntu
Module version: 3.0.0
How to reproduce (e.g Puppet code you use)
class { 'mongodb::globals':
manage_package_repo => true,
repo_location => 'https://our.nexus.server/repository/mongodb-org',
version => '4.2.1',
}
What are you seeing
The packages cannot be installed from the cache.
What behaviour did you expect instead
The packages should be installed from the cache.
Any additional information you'd like to impart
I think this comes from the if-elsif-else block starting at line 34 in manifests/repo.pp, which prohibits further repository configuration if repo_location has been set. However, in case of a Nexus cache, the only thing that changes is the URL. Everything else that goes into the sources.list file should stay the same.
The text was updated successfully, but these errors were encountered:
dhs-rec
changed the title
Installation from mongodb.org apt repository doesn't work if it's cached locally (Nexus)
Installation from local (Nexus) cache of the mongodb.org apt repository doesn't work
Nov 25, 2019
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
The packages cannot be installed from the cache.
What behaviour did you expect instead
The packages should be installed from the cache.
Any additional information you'd like to impart
I think this comes from the
if-elsif-else
block starting at line 34 in manifests/repo.pp, which prohibits further repository configuration if repo_location has been set. However, in case of a Nexus cache, the only thing that changes is the URL. Everything else that goes into the sources.list file should stay the same.The text was updated successfully, but these errors were encountered: