Please tell us what you did, maybe copy your
/etc/foreman-installer/scenarios.d/foreman-answers.yaml (minus host/domain
specifics). I'm having a similar problem and would love to know how you
resolved it.
On Friday, October 14, 2016 at 10:12:03 AM UTC-5, Andrew Enstad wrote:
>
>
> Got it workin
It's good form and good karma to include specifics of what you did to get it
working for the benefit of the herd...
From: "Andrew Enstad"
To: "Foreman users"
Sent: Friday, October 14, 2016 10:12:03 AM
Subject: [foreman-users] Re: Foreman 1.13 install - puppet er
Got it working. I Tried some different options with the foreman-installer
and now Puppet is happy.
On Thursday, October 13, 2016 at 4:35:10 PM UTC-5, Andrew Enstad wrote:
>
> Anyone else having issues with the install of Foreman 1.13?
>
> I have a Centos7 server that I have been trying to insta
There is a Smart Proxy listed and the URL: shows a page with a Sinatra
saying. I do see the following Errors/Warnings:
TCPServer Error: Address already in use - bind(2)
OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=SSLv3 read
client certificate A: tlsv1 alert unknown ca
/usr/sh
On 14/10/16 15:12, Andrew Enstad wrote:
>
> /var/log/foreman/production.log file:
> 2016-10-14 09:09:14 2ac200ec [app] [I] Processing by
> HostsController#externalNodes as YML
> 2016-10-14 09:09:14 2ac200ec [app] [I] Parameters:
> {"name"=>"foreman.quicksand.identix.com"}
> 2016-10-14 09:09:14 2
Here is the output and log file:
Output:
[root@foreman ~]# /etc/puppet/node.rb foreman.quicksand.identix.com
During the fact upload the server responded with: 403 Forbidden. Error is
ignored and the execution continues.
{
"error": {"message":"Access denied","details":"Missing one of the
requir
