Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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: parallel-executor-core: cannot accept event: Dynflow::Director::Event error appears in the satellite-restore for the specific customer database


Version-Release number of selected component (if applicable):
6.9 Snap17 (Problem came in 6.8 satellite restore)

How reproducible:
1/1

Steps to Reproduce:
1. Restore Satellite using 6.8 backup data.
2. Satellite restored successfully
3. Perform upgrade on restored satellite from 6.8 to 6.9.
4. upgrade completed successfully.

Actual results:
Seen step_id: 4, event: Dynflow::Action::Polling::Poll, result: #<Concurrent::Promises::ResolvableFuture:0x00007fc304ffee38 pending>] core is terminating (Dynflow::Error) in the satellite restore.

Expected results:
This error should not come.

Additional info: There is no impact on the satellite restore and upgrade.

Verified with Sat 6.9.3 snap 2.0 and Sat 6.10.0 snap 7.0.

Used reproducer from OP (on a database that only contained a few manually created entities since there is no db or customer case attached) but used 6.9.3 instead of 6.8 and 6.10.0 instead of 6.9. Encountered bug 1978623 but no related errors in the process and the Satellite is now working as 6.10.0.

# mkdir /tmp/bup
# satellite-maintain backup offline /tmp/bup
# satellite-maintain restore /tmp/bup/satellite-backup-2021-07-01-16-19-31/
# satellite-maintain upgrade run --target-version 6.10 --whitelist="repositories-validate,repositories-setup"

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 (Moderate: Satellite 6.10 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/RHSA-2021:4702