Bug #33205
open
Mysql -> Postgres Migration foreman 1.23.1
Description
Hi, i am currently trying to migrate our foreman installation from MySQL to Postgres
packages installed are:
foreman-1.23.2-1.el7.noarch
foreman-cli-1.23.2-1.el7.noarch
foreman-debug-1.23.2-1.el7.noarch
foreman-ec2-1.23.2-1.el7.noarch
foreman-installer-1.23.2-1.el7.noarch
foreman-libvirt-1.23.2-1.el7.noarch
foreman-mysql2-1.23.2-1.el7.noarch
foreman-ovirt-1.23.2-1.el7.noarch
foreman-postgresql-1.23.2-1.el7.noarch
foreman-selinux-1.23.2-1.el7.noarch
foreman-vmware-1.23.2-1.el7.noarch
tfm-rubygem-foreman_hooks-0.3.15-1.fm1_23.el7.noarch
tfm-rubygem-foreman_memcache-0.1.1-2.fm1_23.el7.noarch
tfm-rubygem-foreman_setup-7.0.0-1.fm1_23.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.18.2-1.el7.noarch
the error from the rake task "foreman-rake db:convert:prod2dev --trace" can be found in the attached file foreman_migration.log.
please advise on how to fix this.
Files
Updated by Adam Ruzicka almost 3 years ago
You will need to patch dynflow on that machine with this patch1, it should apply cleanly. Why this needs to be done is described in the patch itself. This patch is included in later releases of dynflow, but the version shipping with foreman 1.23 is rather old.
[1] - https://github.com/Dynflow/dynflow/commit/13d6bcc7afba9e90f74518fb3bf306b7c074ea24.patch