Bug 1940084 - parallel-executor-core: cannot accept event: Dynflow::Director::Event error appears in the satellite-restore for the specific customer database
Summary: parallel-executor-core: cannot accept event: Dynflow::Director::Event error a...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dynflow
Version: 6.9.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: 6.10.0
Assignee: Adam Ruzicka
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-17 15:08 UTC by Devendra Singh
Modified: 2021-11-16 14:10 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-dynflow-1.4.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:10:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github Dynflow dynflow pull 386 0 None open Fix undefined method 'result' error on termination 2021-04-08 10:12:49 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:10:35 UTC

Description Devendra Singh 2021-03-17 15:08:18 UTC
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.

Comment 7 Lukáš Hellebrandt 2021-07-02 10:44:40 UTC
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"

Comment 10 errata-xmlrpc 2021-11-16 14:10:21 UTC
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


Note You need to log in before you can comment on or make changes to this bug.