Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When doing online backup foreman-maintain skips the qpidd and activemq directories,

'/var/lib/qpidd',
'/var/lib/candlepin/activemq-artemis'

There should be some way to automatically create minimal required queues for qpidd and candlepin after restoring the online backup.

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

6.7

How reproducible:

Each time

Steps to Reproduce:
1. Take the online backup.
2. Directories are skipped.
3. The qpidd service may or may not start/work properly.

Actual results:

Qpidd might be having stale data about the queues on restoring online backup.

Expected results:

Qpidd queues should be recreated which are necessary to run the service without any problems.

Additional info:

https://bugzilla.redhat.com/show_bug.cgi?id=1673908#c32

The steps to generate these queues can be found here and should be pulled in-line into foreman-maintain:

https://github.com/RedHatSatellite/satellite-support/blob/master/satellite-reset#L120

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29533 has been resolved.

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 (Satellite 6.8 Satellite Maintenance Release), 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-2020:4365