Marc,
I finally got this to work, I had made one critical mistake and I had to
hack the answer script and answer file a little.
1. I had originally tried to use a rhel 7 instance and change the package
in the script to use a 7 package but that didn't work. So i switched to the
centos 6 instance and I got a different installation error.
2. I had to change the script to use '-c' and not '-a' for the answer file
location
3. I changed the answer file name to pe.conf in /etc/puppetlabs
4. I had to replace all of the '$(hostname -f)' references in the answer
file to "%{::trusted.certname}"
4. I had to add two required variables to the pe.conf file according to
https://docs.puppet.com/pe/latest/install_pe_conf_param.html
"console_admin_password":
"puppet_enterprise::puppet_master_host":
This may be a bad hack, I don't know, but it got it working for me.
Conrad
On Friday, December 23, 2016 at 6:21:32 PM UTC-8, Conrad wrote:
>
> HI everyone,
>
> I'm very new to SCALR, i'm using the open source 5.x version and I tried
> following the tutorial for automating puppet enterprise with scalr
> https://scalr-wiki.atlassian.net/wiki/display/docs/Step+1+-+Installing+Puppet+Enterprise
>
> ; everything went as planned until I launched the farm. I seem to be in an
> infinite loop with the instance never coming up on the network; the
> instance is eventually terminated and a new one is created and goes into
> this same loop. It's been in this loop for about two weeks :). Attached is
> the screenshot of where the initializing keeps hanging. Any ideas or
> direction on what might be causing this would be appreciated, I really want
> to get scalr working in our environment. Thank you.
>
> Conrad
>
--
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
