Bug 1869640

Summary: client-dispatcher: wrong number of arguments (given 0, expected 1..3) (ArgumentError)' messages come in upgrade and installation.
Product: Red Hat Satellite Reporter: Devendra Singh <desingh>
Component: DynflowAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: aruzicka, ehelms, pcreech
Target Milestone: 6.8.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-dynflow-1.4.7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:05:30 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 2020-08-18 12:26:31 UTC 
Description of problem: Client-dispatcher: wrong number of arguments (given 0, expected 1..3) (ArgumentError)' messages come in upgrade and installation.


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

How reproducible:
always

Steps to Reproduce:
1. Upgrade the satellite from 6.7 to 6.8 or install the 6.8 satellite. 
2. During installation or upgrade below error comes in messages.

Aug  7 04:20:04 qesat6811 foreman: E, [2020-08-07T04:20:04.243817 #17766] ERROR -- /client-dispatcher: wrong number of arguments (given 0, expected 1..3) (ArgumentError)
Aug  7 04:20:04 qesat6811 foreman: [ concurrent-ruby ]


Actual results:
client-dispatcher: wrong number of arguments (given 0, expected 1..3) (ArgumentError)

Expected results:
Argument error should not come in clinet-dispatcher.



Additional info:
Comment 1 Adam Ruzicka 2020-08-27 07:26:45 UTC 
This is possibly fixed by Dynflow/dynflow#364, although it is hard to say from just two lines of logs. @Devendra is there more in the logs or is this all we have?
Comment 4 Adam Ruzicka 2020-08-28 11:53:04 UTC 
Upstream fix was merged, moving to POST
Comment 5 Adam Ruzicka 2020-08-29 08:59:09 UTC 
Upstream release 1.4.7 containing fix for this BZ is out, moving to modified.
Comment 6 Lukáš Hellebrandt 2020-09-15 14:57:08 UTC 
Verified with Sat 6.7 => Sat 6.8 snap 15. Tried both upgrade and clean installation, both passed.
Comment 9 errata-xmlrpc 2020-10-27 13:05:30 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 (Important: Satellite 6.8 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-2020:4366
Comment 10 errata-xmlrpc 2020-10-27 13:08:34 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 (Important: Satellite 6.8 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-2020:4366