Thats a tough spot, as you are upgrading through a lot of versions. I would recommend trying to upgrade sequentially to at least 3.2 before jumping up to 3.4. We only test upgrading as far back as N-2.
Eric On Thu, Aug 24, 2017 at 3:58 AM, <ehart...@gmail.com> wrote: > Dear all, > > can someone help me to upgrade my Katello from 2.4.4 to 3.4.4, I´m getting > now the following: > > [ERROR 2017-08-23 22:20:58 main] foreman-rake -- config -k use_pulp_oauth > -v true >/dev/null failed! Check the output for error! > [DEBUG 2017-08-23 22:21:12 main] API controllers newer than Apipie cache! > Run apipie:cache rake task to regenerate cache. > [DEBUG 2017-08-23 22:21:44 main] rake aborted! > [DEBUG 2017-08-23 22:21:44 main] StandardError: An error has occurred, > this and all later migrations canceled: > [DEBUG 2017-08-23 22:21:44 main] > [DEBUG 2017-08-23 22:21:44 main] The single-table inheritance mechanism > failed to locate the subclass: 'Katello::System'. This error is raised > because the column 'type' is reserved for storing the class in case of > inheritance. Please rename this column if you didn't intend it to be used > for storing the inheritance class or overwrite > HostCollectionToHosts::System.inheritance_column to use another column > for that information./opt/rh/sclo-ror42/root/usr/share/gems/ > gems/activerecord-4.2.5.1/lib/active_record/inheritance.rb:186:in `rescue > in find_sti_class' > [DEBUG 2017-08-23 22:21:44 main] ActiveRecord::SubclassNotFound: The > single-table inheritance mechanism failed to locate the subclass: > 'Katello::System'. This error is raised because the column 'type' is > reserved for storing the class in case of inheritance. Please rename this > column if you didn't intend it to be used for storing the inheritance class > or overwrite HostCollectionToHosts::System.inheritance_column to use > another column for that information. > [DEBUG 2017-08-23 22:21:44 main] NameError: uninitialized constant > Katello::System > [ERROR 2017-08-23 22:21:44 main] foreman-rake db:migrate failed! Check the > output for error! > [ERROR 2017-08-23 22:22:02 main] foreman-rake -- config -k use_pulp_oauth > -v false >/dev/null failed! Check the output for error! > [ERROR 2017-08-23 22:22:02 main] Upgrade step migrate_foreman failed. > Check logs for more information. > [DEBUG 2017-08-23 22:22:02 main] Exit with status code: 1 (signal was 1) > [ERROR 2017-08-23 22:22:02 main] Errors encountered during run: > [ERROR 2017-08-23 22:22:02 main] foreman-rake -- config -k use_pulp_oauth > -v true >/dev/null failed! Check the output for error! > [ERROR 2017-08-23 22:22:02 main] foreman-rake db:migrate failed! Check the > output for error! > [ERROR 2017-08-23 22:22:02 main] foreman-rake -- config -k use_pulp_oauth > -v false >/dev/null failed! Check the output for error! > [ERROR 2017-08-23 22:22:02 main] Upgrade step migrate_foreman failed. > Check logs for more information. > > Thanks, > Christian > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscr...@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
