[foreman-users] Re: Install Katello with external SSL CA

Hello Pascal, Thanks for your answer, I've tried that too, this works great for replacing Katello/Foreman Web SSL certificate and also for the smart proxy but not for puppet. I wanted to disable the puppet ca and use the one provided by freeIPA. I've tried to replace the puppet certificate by

[foreman-users] Re: Did foreman-vmware works with VMWare vSphere 6.5 ?

vsphere 6.5 is working as expected for for me with foreman-1.14.3 except no VNC console.I'm using vcenter server appliance 6.5. Thanks Laxman On Monday, May 15, 2017 at 8:58:05 AM UTC-4, Quin wrote: > > Good evening together, > > we have created a new infrastructure with VMWare vSphere

[foreman-users] Re: Did foreman-vmware works with VMWare vSphere 6.5 ?

On Monday, May 15, 2017 at 8:58:05 AM UTC-4, Quin wrote: > > Good evening together, > > we have created a new infrastructure with VMWare vSphere 6.5. > I want to add the new resource (type "VMWare") in Foreman. After i write > my login data to the fields and click on "load datacenters" it said

[foreman-users] cockpit integration with foreman

Hello, I installed cockpit and tfm-rubygem-foreman_cockpit.noarch in foreman server. I'm using foreman-1.15.0 I got below error when click on the host in foreman.do I need to change any configuration for cockpit in foreman? Please help me *Oops, we're sorry but something

[foreman-users] Re: Foreman 1.14.3 UI - Cannot create new host (or provision a new host from a discovered host)

LOL, with debugging on we quickly found the issue: 2017-05-19 12:05:01 0c04f9fc [app] [W] Unable to render PXELinux template 'custom_Ubuntu_PXELinux': undefined local variable or method `request' for # | NameError: undefined local variable or method `request' for # |

Re: [foreman-users] Re: Occasional ERF50-7522 on facts_refresh

> unless new_host && hostgroup.nil? && respond_to?(:reports) && > reports.empty? > > Well, that's what I was trying to tell you - this patch did not work for me. I tried it out as you suggested on May 3rd, the only difference it made is the error message changed from Discovered by URL:

[foreman-users] VMs being deleted immediatelyafter provisioning in 1.15.0

After upgrading to 1.15.0 I am unable to provision VMware VMs with Foreman. After creating the node in Foreman it successfully brings the VM up in VMware and then immediately deletes it. It seems to be related to Foreman scheduling a compute instance update. Log output below:

Re: [foreman-users] Re: PXE boot never ending after apdating from 1.14.3 to 1.15.0

No I dodn't try that. Usually i clone kickstart redhat template to create customized kickstart templates. I missed that built option in customized kickstat file. Thanks Laxman On Fri, May 19, 2017 at 4:53 AM Lukas Zapletal wrote: > > On Fri, May 19, 2017 at 4:05 AM, laxman

[foreman-users] Foreman TLV meetup

Hello all, In celebration of Foreman 1.15 release we will be holding a meetup in the Red Hat offices in Israel. The meetup will be on June 7th between 17:30 and 21:00 IST. The office is located at 34 Yerushalaim Rd, Raanana, Israel. So far we have confirmed: - two international speakers - two

Re: [foreman-users] Re: Occasional ERF50-7522 on facts_refresh

On Fri, May 19, 2017 at 10:54 AM, Lukas Zapletal wrote: > unless new_host && hostgroup.nil? && reports.nil? && reports.empty? Sorry I mean: unless new_host && hostgroup.nil? && respond_to?(:reports) && reports.empty? Send a PR to discuss this with Greg for a proper fix, this

Re: [foreman-users] Re: Occasional ERF50-7522 on facts_refresh

Well, you can easily fix this, I thought it is obvious sorry: https://github.com/theforeman/foreman_default_hostgroup/blob/develop/lib/default_hostgroup_base_host_patch.rb#L66 change to: unless new_host && hostgroup.nil? && reports.nil? && reports.empty? On Fri, May 19, 2017 at 12:56 AM,