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:
Clicking on the Dynflow console button in a task, before API calls are complete, yields an Internal Server Error
Version-Release number of selected component (if applicable): 6.7
How reproducible: 100%
Steps to Reproduce:
1. Create a task
2. (quickly) as the task page loads, click the dynflow console button
3.
Actual results: The URL changes to something like
https://<server_url>/foreman_tasks/dynflow/null and an Internal Server Error is seen
Expected results: Button should be disabled until the page has loaded the appropriate data
Additional info:
Comment 5Lukáš Hellebrandt
2021-01-25 14:57:26 UTC
Verified with Sat 6.9 snap 8.0. I wasn't able to reproduce this (the task was syncing a product) - either I'm not quick enough or it is fixed. I take the liberty of supposing the latter.
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.9 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:1313