Foreman Maintain

Cloned from BZ:

Description of problem:
When cloning a Red Hat Satellite 6.6 without pulpdata the

Version-Release number of selected component (if applicable):

Redhat Satellite 6.6
qpid-tools-1.36.0-28.el7amq.noarch
tfm-rubygem-qpid_messaging-1.36.0-9.el7sat.x86_64
qpid-cpp-server-1.36.0-28.el7amq.x86_64
python-qpid-qmf-1.36.0-28.el7amq.x86_64
qpid-cpp-client-1.36.0-28.el7amq.x86_64
qpid-dispatch-router-1.5.0-4.el7.x86_64
python-qpid-1.35.0-5.el7.noarch
qpid-cpp-client-devel-1.36.0-28.el7amq.x86_64
qpid-proton-c-0.28.0-1.el7.x86_64
qpid-cpp-server-linearstore-1.36.0-28.el7amq.x86_64
qpid-qmf-1.36.0-28.el7amq.x86_64
python-gofer-qpid-2.12.5-5.el7sat.noarch
python-qpid-proton-0.28.0-1.el7.x86_64

How reproducible:

Steps to Reproduce:
1. Install Red Hat Satellite 6.6 , sync some content and create a backup without pulp content
2. Use Satellite Clone to clone and restore and see the installer fail with qpid trying to start up

Actual results:
qpid hangs during start up and passes the installer timeout duration and causes the puppet-installer to fail leaving the box in an error state.

Expected results:
Clone and restore to finish correctly

Additional info:

From talking to Pavel, it looks like qpid is starting correctly but not listening so it hangs.

qpidd loads plugins, first linearstore, then ACL, then SSL - and the loading of linearstore that processes durable queues had to fail in some way, causing further plugins were not loaded
so the journals must be damaged.

workaround: rm -f /var/lib/qpidd/.qpidd/qls/dat2/*
info about queues etc shall not be touched