Description of problem: After restoring satellite backup using satellite-clone utility, upon login to webui/accessing "All Hosts" and "Content Hosts" page fails with error : 2017-11-17 14:53:59 1663b3d9 [app] [W] Action failed | ActiveRecord::SubclassNotFound: The single-table inheritance mechanism failed to locate the subclass: 'HostStatus::ExecutionStatus'. 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 HostStatus::Status.inheritance_column to use another column for that information. | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/inheritance.rb:161:in `rescue in find_sti_class' | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/inheritance.rb:155:in `find_sti_class' | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/inheritance.rb:144:in `discriminate_class_for_record' - Is this a possible bug with clone utility? - Tried to execute satellite-installer with --upgrade and it was successful but issue still persists Version-Release number of selected component (if applicable): Satellite 6.3 Snap 24 Steps to Reproduce: 1. Took backup of working satellite v 6.2 using katello-backup 2. Installed fresh RHEL 7 system and executed satellite-clone task "ansible-playbook satellite-clone-playbook.yml" 3. Login worked successfully but unable to access "All Hosts" and "Content Hosts" page. While accessing it fails with above traceback.
After some discussion, REX can be enabled in a clone w/o issue. This change was added here: https://github.com/RedHatSatellite/satellite-clone/pull/273
This actually didn't make it into 1.2.0, but is merged upstream https://github.com/RedHatSatellite/satellite-clone/pull/273
Verified in satellite-clone-1.2.1-1.el7sat.noarch All Hosts, Content Hosts pages are now accessible in the cloned server.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0330