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: 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:
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?
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
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