-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
6.14.0
Description of problem:
Unexpected dynflow error messages appear in /var/log/foreman/production.log after clean installation and default satellite-installer
Version-Release number of selected component (if applicable):
Satellite 6.14 SNAP22
How reproducible:
always
Steps to Reproduce:
1. prepare a machine suitable for Satellite
2. install satellite package using yum/dnf
3. perform satellite installer (e.g. satellite-installer --scenario satellite --foreman-initial-admin-password abc)
Actual results:
Errors in /var/log/foreman/production.log
2023-11-01T09:47:06 [E|dyn|] Failed to run hook 'log_task_state_change' for action 'Actions::CheckLongRunningTasks'
(+traceback)
...
2023-11-01T09:47:06 [E|dyn|] PG::TRSerializationFailure: ERROR: could not serialize access due to read/write dependencies among transactions
| DETAIL: Reason code: Canceled on identification as a pivot, during conflict out checking. |
| HINT: The transaction might succeed if retried. |
| (ActiveRecord::SerializationFailure) (+traceback) ... 2023-11-01T09:48:23 [E\|dyn\|] Could not load execution plan e0a7ec95-f659-4b32-a823-bc5066673eeb 2023-11-01T09:48:23 [E\|dyn\|] Could not load steps for execution plan e0a7ec95-f659-4b32-a823-bc5066673eeb (Dynflow::Errors::DataConsistencyError) (+traceback) |
Expected results:
No errors in production log during default installation.
Additional info:
The output of satellite-installer does not contain any errors. Similar errors appear during disconnected installation and also for nightly (Satellite 6.15)