-
Notifications
You must be signed in to change notification settings - Fork 21
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
apt repo issue (no puppet-agent found) trying to install puppet 4.3.1 #32
Comments
Weird, on precise boxes the version number is "1.3.2-1trusty", I'll have to take that into account in the install script... |
Hi there... I ended up having more problems.. It appears that the ubuntu/trusty64 image has a version of puppet already installed.. I'm not sure why this is this way (maybe to support the provision puppet. Anyways, I thought I'd let you know what I ended up needing to do (in the event it helps out at all).
Included the following script .. (I have shared the part I can with you).
Now, everything is installed perfectly (based on the new version 4.X directory structure). You'll find now that puppet is located in the following location...
and etc. files...
If using 'ubuntu/trusty64' is a bad idea for this plugin, I suppose you could always restrict to particular boxes.. Up to you. I hope this info helps you out. |
@MikeCaspar It's possible to use this plugin to run a script of your choice, so you could integrate this in the Vagrantfile using the plugin. For example this worked for me: (Gist link is to your above code) config.vm.define :trusty_ubuntu_box do |trusty_ubuntu_box|
trusty_ubuntu_box.puppet_install.puppet_version = :latest
trusty_ubuntu_box.puppet_install.install_url = 'https://gist.githubusercontent.com/petems/6723c2eedb9d32d7ad97/raw/990ff448f6430aa015e208668a3cecb3f1db0d4b/purge_old_install_new.sh'
trusty_ubuntu_box.vm.box = "ubuntu/trusty64"
trusty_ubuntu_box.vm.provision "shell", inline: "puppet --version"
end Can you confirm if that works for you? |
* Catches #32 * Uses @MikeCaspar's code to clear out pre-installed Puppet
Hi there. Things worked out well !! Thanks. There is one Tiny quirk (not sure if its worth trying to change ? I think I'll leave it for now). The user vagrant has the path added to the shell of "/opt/puppetlabs/bin/" nicely. For some reason, the path change didn't copy over to the root user. This is the Default behaviour though, so not sure how big of a deal this is. I like the idea of the gist by the way :-> Nice approach. I've created a repo for the future in the event this script should be improved over time (which I suspect it might be.). It could also serve other people as well.. I'll add you as a contributor to the repo... I put a license on it (MIT) as it's fairly destructive in nature. repo This would make the new config...
Feel free to add yourself as a contributor to the README.MD any time. Here's the repo [https://github.com/MikeCaspar/vagrant-purge-old-puppet-from-ubuntu] https://github.com/MikeCaspar/vagrant-purge-old-puppet-from-ubuntu |
Hi, just so you know. I created a /latest so you don't have to adjust the versions unless you want to. |
👍 |
Have tried installed with a specific version number as well as latest.
After some experimentation found a way to install...
Error...
I found this in the output which gave me clue....
Eventually, I managed to get the puppet agent to install by using the instructions on this page from puppetlabs...
I'm not sure if the problem is the reference to trust or wheezy, but by following the instructions, I did the following...
My Vagrantfile uses...
From what I can tell, the script command could be the problem.
I just thought I'd share here as a problem with some clues as to where it might get fixed.
The text was updated successfully, but these errors were encountered: