Re: [foreman-users] Foreman server migration

2017-03-08 Thread pascalp
Hello, you could drop the schema after logging in as it's owner (postgres user I assume). The following command drops the schema and all tables: DROP SCHEMA public CASCADE; And then import again. Alternatively you could try to grant your foreman database user permissions for public schema:

Re: [foreman-users] Foreman server migration

2017-03-07 Thread James Denton
Hi I backed up the Postgresql DB on our active server and restored on the new RHEL 7 server using the instructions in the Foreman manual (https://theforeman.org/manuals/1.14/index.html#5.5Backup,RecoveryandMigration), however i receive the following errors: [root@test ~]# foreman-rake

Re: [foreman-users] Foreman server migration

2017-03-07 Thread James Denton
Thanks Josh, what is the best way to migrate all the puppet modules? On Monday, March 6, 2017 at 12:56:14 PM UTC, Josh wrote: > > The easiest way to do this is to simply take a backup of your Foreman > database and re-import it into your new Foreman instance. > > On Mon, Mar 6, 2017 at 5:35 AM,

[foreman-users] Foreman server migration

2017-03-06 Thread James Denton
Hi As later versions of Foreman are no longer supported on RHEL6 we have decided to build a new Foreman/Puppet master server on RHEL7 with the latest versions. Is there any documentation, previous questions on how to migrate current Foreman specific files/data including for example - nodes,