[foreman-users] Pulp internal server error

Hi all, I'm pretty new to Katello and Foreman and since I've updated pulp to the latest version I'm not able to use any function/feature of it, Katello/foreman throws always the following error: There was an issue with the backend service pulp: 500 Internal Server Error I've tried to debug wh

[foreman-users] Re: How can I automate Install puppet agent on host after provisioning

Hi, What kind of host you're deploying Windows / Linux / other? You have to use the appropriate provisioning template which includes the installation of puppet agent. For example using kickstart template to deploy redhat/centos linux includes the installation of puppet agent. rgds, Arsène On

[foreman-users] Re: Pulp internal server error

Same happened to me yesterday, but I had forgotten to run: foreman-installer --scenario katello --upgrade Did you run this part? If not, this would be the reason for your problem. You could verify this by looking at /var/log/foreman/production.log. Your 500 errors will look similar to: 2017

[foreman-users] Re: Pulp internal server error

Many thanks Duncan it did it ! I forgot to run that command Regards, Arsène On Tuesday, July 18, 2017 at 10:13:05 AM UTC+2, Duncan Innes wrote: > > Same happened to me yesterday, but I had forgotten to run: > > foreman-installer --scenario katello --upgrade > > Did you run this part? If no

[foreman-users] foreman-ansible callback

Hi, I am lost with setting of callback/foreman.py. We use Foreman 1.15.2, Katello 3.4.2, foreman_ansible 1.4.5 (with updated callback/forman.py from github) and ansible 2.3.1 on CentOS 7. I think i know where Foreman runs. curl -k -H "Accept: application/json" https://fqdn.in.corp/status {"re

Re: [foreman-users] foreman-ansible callback

On 07/18, Dan Sk wrote: > > > Hi, > > I am lost with setting of callback/foreman.py. > > We use Foreman 1.15.2, Katello 3.4.2, foreman_ansible 1.4.5 (with updated > callback/forman.py from github) and ansible 2.3.1 on CentOS 7. > > I think i know where Foreman runs. > curl -k -H "Accept: applicati

[foreman-users] selecting foreman-proxy puppet for registration

Currently we have multiple foreman-proxies that handle the puppet service. We have a specific one that doesn't have a lot of resources and is just meant to be used for servers that are behind a private network. One problem we are having is that any new server registrations are getting setup unde

[foreman-users] foreman-proxy: port for local test environments open

Hi, per default, the http_port for local test environments in foreman-proxy is open: In file /etc/foreman-proxy/settings.yml -- # activated for creating local test environments :http_port: 8000 -- Does this make sense? Are there any drawbacks if this configuration option is remove

[foreman-users] Re: Smartproxy PuppetCA never triggered

I have successfully tested this. Calling curl foreman_url('provision') returns "No provisioning template found for host x". But the autosign entry still gets created. That's good, opens options :). -- You received this message because you are subscribed to the Google Groups "Foreman users"