-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install older version if EPEL present #258
Comments
For now, I have been able to do the following:
and
|
I had nodes that were running a really old version (0.10 ), which I was trying to upgrade to 6.x and had only specified the repo_url_suffix based on the module README.md . This worked great on test nodes that had no previous install, however it skipped the install on the nodes that had an old version. @tapsboy solution worked great for me, but took a little digging to find it. The nodejs_package_ensure parameter is listed in the README.md, but might be good to emphasize that it defaults to present and specifying a repo_url_suffix is not sufficient to ensure a specific major version. |
EPEL recently updated the current node version available there. More info here (https://fedoramagazine.org/node-js-6-x-lts-coming-epel-7/)
As a result, when puppet runs
/bin/yum -d 0 -e 0 -y install nodejs
, it installs the one available in EPEL and not the one requested by the module. This wasn't a problem earlier as EPEL was on 0.10.Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Or
What are you seeing
It always installs latest version from v6 branch
What behaviour did you expect instead
The version specified, while requiring the nodejs class
Any additional information you'd like to impart
I believe this is happening because the module doesn't specify the source or exact version to be picked up in the install.pp
The text was updated successfully, but these errors were encountered: