Re: [foreman-users] IPv6 support

1.13 has some form of IPv6 support. Is pxeboot possible over IPv6 now or is it still pending? We're looking at IPv6 pxe booting RHEL7 EFI, if anyone has any pointers or a guide that could help us that would be great. Regards Matt W On Wednesday, April 22, 2015 at 1:03:14 AM UTC+10, Lukas

[foreman-users] Re: Error while clustering Foreman | HA Foreman & puppet

I would start by reading those two posts, they are quite good. https://theforeman.org/2015/12/journey_to_high_availability.html https://deviantony.wordpress.com/2014/06/21/setup-a-scalable-puppet-environment-with-foreman-on-ubuntu-12-04/ (The only thing i dislike about this post is that he uses

[foreman-users] Re: Error while clustering Foreman | HA Foreman & puppet

Just now I have seen foreman is running on host1.example.com instead of foremandv.example.com. The reason I choose generic name so that I can cluster the foreman servers, but foreman is running based on hostname specific. Can you please guide me. Thank you On Tuesday, November 22, 2016 at

[foreman-users] Re: Error while clustering Foreman | HA Foreman & puppet

Appreciate your quick reply. Yes I have replaced host1.example.com with foremandv.example.com in the answer file and ran the installer. I have generated the certs in the name of foremandv.example.com and copied to this host1.example.com. I have one more node where it acts as puppet ca +

[foreman-users] Re: Error while clustering Foreman | HA Foreman & puppet

You already ran the installer, then modified the answer file and replaced host1.example.com with foremandv.example.com? If you can give more details it will be much more helpful. But simple as the error state, the smart proxy is using a certificate with an CN attribute that does not match the

[foreman-users] Error while clustering Foreman | HA Foreman & puppet

Hello, I have dedicated puppet ca where I have generated certs in the name of foreman url which I want to and copied /etc/puppetlabs/puppet/ssl/certs/ca.pem , foreman.example.com.pem and */private_keys/foremandv.example.com.pem and crl.pem. to host1.example.com. " host1.example.com" using

Re: [foreman-users] Plugin Job: All Jobs i run failed

Hi Adam, you give me the right hint to find the solution and your first idea was the right one... [2016-11-22 14:38:01.861 #119088] ERROR -- action: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca (OpenSSL::SSL::SSLError)

Re: [foreman-users] Re: Foreman plugin dependency problem with "deface".

On 22 November 2016 at 08:29, Doug Scoular wrote: > Hi Greg, > > That helps heaps! > > I'm curious as to why the "production" 1.12 machine which uses a remote > puppet CA, puppet Compile Master and DB didn't already have a dependency on > "deface". I guess maybe the

Re: [foreman-users] Plugin Job: All Jobs i run failed

Hello, it seems that when the proxy is making a callback to Foreman, it doesn't reach Foreman at all. Could you please set set log_level to DEBUG in /etc/smart_proxy_dynflow_core/settings.yml, watch the log in /var/log/foreman-proxy/smart_proxy_dynflow_core.log and try to rerun the job? Some

Re: [foreman-users] Re: Foreman plugin dependency problem with "deface".

Hi Greg, That helps heaps! I'm curious as to why the "production" 1.12 machine which uses a remote puppet CA, puppet Compile Master and DB didn't already have a dependency on "deface". I guess maybe the foreman_setup plugin doesn't use it. Anyway, I'm now furiously trying to learn ruby so I can