[foreman-users] Unable to get environments from Puppet. Foreman 1.12.1 Puppet 3.8.7 After upgrade.

After upgrading from Foreman 1.11.1 & Puppet 3.8.3. When I try to import classes I get an error popup: Error: ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([RestClient::NotAcceptable]: 406 Not Acceptable) for proxy https://vm-puppet.test.local:8443/puppet wh

[foreman-users] Re: Unable to get environments from Puppet. Foreman 1.12.1 Puppet 3.8.7 After upgrade.

d: Forbidden request: vm-puppet.test.local(127.0.1.1) access to /v2.0/environments [find] at :119","issue_kind":"FAILED_AUTHORIZATION"} On Wednesday, August 10, 2016 at 10:11:24 AM UTC-4, Michael Hurn wrote: > > After upgrading from Foreman 1.11.1 & Puppet

[foreman-users] Re: Unable to get environments from Puppet. Foreman 1.12.1 Puppet 3.8.7 After upgrade.

rieve the certificate they requested earlier path /certificate/ auth any method find allow * # allow nodes to request a new certificate path /certificate_request auth any method find, save allow * path /v2.0/environments method find allow * # deny everything else; this ACL is not strictly necessar

[foreman-users] Re: Unable to get environments from Puppet. Foreman 1.12.1 Puppet 3.8.7 After upgrade.

eps I took to do the upgrade. I may have missed one or two! ;) On Wednesday, August 10, 2016 at 10:11:24 AM UTC-4, Michael Hurn wrote: > > After upgrading from Foreman 1.11.1 & Puppet 3.8.3. > > When I try to import classes I get an error popup: > > > Error: ERF12-2749 [Pro

[foreman-users] Re: how to upgrade 1.12.1 to 1.12.2

Hi Erik, It looks like you may have gone too deep with Foreman. The manual gives us a very good guide. https://theforeman.org/manuals/1.12/index.html#3.6Upgrade In short on RedHat/CentOS systems stop foreman & proxy, run yum upgrade and restart Foreman. I have upgraded Foreman a few times. I th

[foreman-users] Foreman 1.12.3 - Error checking out Infrastructure -> Smart proxies 'Puppet' tab

I get this error on Foreman 1.12.3 but not on Foreman 1.12.2 I also get the error on new install and on an upgrade from 1.12. Looks to me that the SQL is missing `smart_proxies` after FROM `hosts`

Re: [foreman-users] Foreman 1.12.3 - Error checking out Infrastructure -> Smart proxies 'Puppet' tab

Thank you Dominic, I was able to follow the links and patch my systems. On Tuesday, September 27, 2016 at 2:59:36 AM UTC-4, Dominic Cleal wrote: > On 26/09/16 23:18, Michael Hurn wrote: > > > > I get this error on Foreman 1.12.3 but not on Foreman 1.12.2 > > > >

Re: [foreman-users] Re: Unable to get environments from Puppet. Foreman 1.12.1 Puppet 3.8.7 After upgrade.

Suh wrote: > Hey Michael, > > Not sure if you ever resolved this problem, but you may want to check the > contents of /etc/foreman-proxy/settings.d/puppet_proxy_legacy.yml and > make sure it's correct. > > > On Thursday, August 11, 2016 at 12:03:07 PM UTC-7, Michael Hu

[foreman-users] Foreman life cycle upgrade Puppet 3.x to 4.x

I am still working on details for this idea: On a CentOS 6 host: We have an all-in-one Foreman 1.12.3 / Puppet 3.8.x with an external MySQL foreman database, that has been upgraded (OS, Foreman & Puppet) a few times. We want to keep the configuration information from the old server to

[foreman-users] Re: Foreman 1.15.0 released

Is it time to update the web site? It still has RC2! On Thursday, May 11, 2017 at 7:14:04 PM UTC-4, Daniel Lobato wrote: > > Foreman 1.15.0 is now available, the latest major release containing > support for notifications, many improvements on VMWare and > provisioning of bonded interfaces, and

[foreman-users] Re: Unable to install foreman-proxy 1.12

I had the same issue - but I have a work-a-round at least one that works for me. Above that: This may help if my memory is correct I think that there was a Katello CentOS repo to help those of us who are unable to upgrade to CentOS 7. Even if it is not up-to-date it could help. When 1.12

[foreman-users] Foreman 1.12 + Puppet 5

Anyone else playing with Puppet 5? I am trying to see if I can get Foreman 1.12.x installed on CentOS 7.3. (I know Foreman 1.12.x is not up-to-date but I need to work with our legacy CentOS 6.x server.) yum -y install http://yum.puppet.com/puppet5/el/7/x86_64/puppet5-release-5.0.0-1.el7.noarch.

[foreman-users] Re: Puppet 3 to 4 Upgrade - Foreman with Separate CA

Hi Jason, I am in the process of doing this from CentOS 6.x, Foreman 1.12.3 with Puppet 3.x. I don't have all your details but I am working on a life cycle upgrade at the moment. I suggest: 1. Upgrade Foreman servers to 1.12.4. 2. Build a new Foreman all-in-one (but without a CA or DB

[foreman-users] rake aborted! foreman-rake db:seed

Two things that may help until an expert can give some imput I recommend all ways using FQDNs for the host and server names. It’s ok if you do not have DNS just add the entries to the local hosts file Also did you set up the foreman account in Postgres? When you use an external db the user acc

[foreman-users] Re: rake aborted! foreman-rake db:seed

sing FQDNs. Good luck with Foreman. Regards, Mike. On Wednesday, October 18, 2017 at 3:59:29 AM UTC-4, Sam Amara wrote: > > Hi, > > Yes I'm using FQDN and all configuration for user account and access > permissions have been added. > > Regards, > > Le mercredi 18