Bug 1940084

Summary:	parallel-executor-core: cannot accept event: Dynflow::Director::Event error appears in the satellite-restore for the specific customer database
Product:	Red Hat Satellite	Reporter:	Devendra Singh <desingh>
Component:	Dynflow	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.9.0	CC:	ahumbe, aruzicka, egolov, zhunting
Target Milestone:	6.10.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tfm-rubygem-dynflow-1.4.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-16 14:10:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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