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.
Bug 1840218 - ArgumentError: wrong number of arguments
Summary: ArgumentError: wrong number of arguments
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dynflow
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks: 1757317
TreeView+ depends on / blocked
 
Reported: 2020-05-26 15:01 UTC by Lukáš Hellebrandt
Modified: 2020-10-27 13:02 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-dynflow-1.4.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:02:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
dynflow-log (30.15 KB, text/plain)
2020-05-26 15:01 UTC, Lukáš Hellebrandt 		no flags Details
production.log (744.42 KB, text/plain)
2020-05-27 09:34 UTC, Lukáš Hellebrandt 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github Dynflow dynflow pull 356 0 None closed Do not instantiate an exception to check its class 2020-10-28 17:41:16 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:02:57 UTC

Description Lukáš Hellebrandt 2020-05-26 15:01:32 UTC 
Created attachment 1692303 [details]
dynflow-log

Description of problem:
I don't know what caused it but I found multiple instances of the attached error and traceback in dynflow log (journalctl -u dynflow-sidekiq@*).

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

How reproducible:
Happened once.
Comment 1 Adam Ruzicka 2020-05-27 07:31:20 UTC 
Could we get production.log from roughly that time?
Comment 2 Lukáš Hellebrandt 2020-05-27 09:34:41 UTC 
Created attachment 1692617 [details]
production.log

Attached. There are tracebacks at 2020-05-26T08:35:39, 2020-05-26T10:53:02, 2020-05-26T10:53:39. I've been syncing 3 repositories at the time.
Comment 4 Adam Ruzicka 2020-06-17 14:18:34 UTC 
Fix for this BZ just went out in dynflow-1.4.5. It would be great if we could pull it into 6.8
Comment 5 Adam Ruzicka 2020-06-17 14:23:14 UTC 
Attaching link to the fix for reference
Comment 6 Lukáš Hellebrandt 2020-07-02 14:22:23 UTC 
Verified with Sat 6.8 snap 7.0. This happened consistently until snap 7.0 and now it doesn't anymore.
Comment 9 errata-xmlrpc 2020-10-27 13:02:46 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
Note You need to log in before you can comment on or make changes to this bug.