Support Vagrant for puppet-pixelated repo
shyba opened this issue · comments
From @varac on November 30, 2015 12:48
We had a Vagrantfile in pixelated-platform, so we should have one in out new puppet-pixelated repo as well
Copied from original issue: pixelated/pixelated-platform#139
From @cz8s on November 30, 2015 12:57
the old Vagrantfile didn't do anything useful. What would you expect from a Vagrant file to set up?
A dispatcher? A platform? A user-agent?
From @varac on February 8, 2016 13:39
done, see https://github.com/pixelated/puppet-pixelated#testing-pixelated
From @bwagnerr on February 12, 2016 18:46
Problems I've found:
- Leap suggests that you add example.org and some other things to the /etc/hosts, trying to access them afterwards didn't work. I had to access https://localhost:8080 and https://localhost:4443.
- Most of the times, when we do the deploy after adding pixelated, apt update fails with "100 reading packages..." and the user agent is never installed, the instructions still tell the user to add things to hosts and try it, but there's no pixelated at all in the installation. Trying the last deploy step several times, I've managed to get the deploy running properly 10 minutes after the installation, after about 15 tries.
Warnings I Got:
- Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
- Warning: Scope(Class[Site_config::Packages]): Could not look up qualified variable '::site_config::params::environment'; class ::site_config::params has not been evaluated
- Warning: Found multiple default providers for vcsrepo: bzr, cvs, dummy, git, hg, svn; using bzr
From @varac on February 25, 2016 15:16
I fixed two of the warnings, for the third one (... class ::site_config::params has not been evaluated) i made a LEAP pull req
I fixed most of the issues @bwagnerr pointed out in #18 (comment).
The issue with the failing apt-get update is still not solved, I made a extra issue for this
Ready again for QA.
To QA, please follow the instructions here: https://github.com/pixelated/puppet-pixelated#testing-pixelated
okay so this is working when using vagrant 1.8.0 or above
The puppet-pixelated parts are not run if using vagrant 1.7.x
@varac I would say either update the readme to ask them to install vagrant 1.8.x or add provisions for older versions of vagrant... then the issue can be closed...
For now, I'm moving it back to ready.
@mnandri
- I fixed the annoying
stdin: is not a ttyerror. - I moved the pixelated provisioning into leap_platform, see
vagrant/add-pixelated.shand the Vagrantfile changes in leap_platform. - I needed to mofify our
vagrant_platform.shscript as well.
Please try again.
Had an issue with old vagrant version. See leapcode/leap_platform#104
ok, leapcode/leap_platform#104 is merged, you can try again.
vagrant provision fails on my box with this error:
==> leap_platform: VM not created. Moving on...
==> pixelated: Running provisioner: shell...
pixelated: Running: inline script
==> pixelated: Running provisioner: puppet...
Shared folders that Puppet requires are missing on the virtual machine.
This is usually due to configuration changing after already booting the
machine. The fix is to run a `vagrant reload` so that the proper shared
folders will be prepared and mounted on the VM.
But vagrant up works
okay, vagrant provision fails reproducably with vagrant 1.6.5.
If I run vagrant reload before, it works.
this is because the old versions of vagrant/virtualbox.
I had vagrant 1.6.5 and virtualbox 4.3. These need the reload.
Reload is not needed with vagrant 1.8.1 and virtualbox 5.0
fix works.
It even works without the fix if using vagrant from hashicorp and virtualbox 4.3