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
When using this on a fresh machine, the install stage ends up breaking the entire puppet run if it can't install any of the dependencies. On CentOS 6, the 'libyaml-devel' package is only available out of the EPEL repos and I'm using the stahnma/puppet-module-epel module to manage the EPEL repo on the machines I'm working with.
Since the rvm-install stage is before main, the package install fails which then blocks the main stage from running and preventing the installation of the EPEL repos on the machine.
Is having the install stage necessary?
The text was updated successfully, but these errors were encountered:
Thank you. Unfortunately that method breaks when you're doing "include epel" in other modules as then you end up with a duplicate class definition in the catalog.
As it may break things for other people, I'll create a fork so that doesn't impact you or any one else to remove the stage.
When using this on a fresh machine, the install stage ends up breaking the entire puppet run if it can't install any of the dependencies. On CentOS 6, the 'libyaml-devel' package is only available out of the EPEL repos and I'm using the stahnma/puppet-module-epel module to manage the EPEL repo on the machines I'm working with.
Since the rvm-install stage is before main, the package install fails which then blocks the main stage from running and preventing the installation of the EPEL repos on the machine.
Is having the install stage necessary?
The text was updated successfully, but these errors were encountered: