Bug 1719765 - Job page is blank after job cancel or job abort on Firefox
Summary: Job page is blank after job cancel or job abort on Firefox
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.6.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.6.0
Assignee: Adam Ruzicka
QA Contact: Peter Dragun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-12 13:55 UTC by Vladimír Sedmík
Modified: 2019-10-22 19:51 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman_remote_execution-1.8.0.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:51:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
printscreen (167.69 KB, image/png)
2019-06-12 13:55 UTC, Vladimír Sedmík
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27566 0 Normal Closed Job page is blank after job cancel or job abort on Firefox 2021-02-10 17:09:06 UTC

Description Vladimír Sedmík 2019-06-12 13:55:33 UTC
Created attachment 1579835 [details]
printscreen

Description of problem:
When cancelling or aborting a future or recurring job, blank page is displayed. This happens on Mozilla Firefox only and is a regression compared to Satellite 6.4.3, where this bug does not occure.

Version-Release number of selected component (if applicable):
satellite-6.6.0-5.beta.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Go to Monitor > Jobs > Run Job button
2. Schedule any future or reccuring job with future start time
3. Click top-right button Cancel Job or Abort Job

Actual results:
Blank page is displayed.

Expected results:
Page with job details should be displayed.

Additional info:
See attachment
After page refresh the job details are displayed.

Tested browsers:
Mozilla Firefox 67.0 (64 bit) - NOK
Google Chrome Version 74.0.3729.169 (Official build) (64bit) - OK
Opera Version: 60.0.3255.151 - OK

Comment 5 Marek Hulan 2019-08-09 06:55:53 UTC
This is reproducible, the error in js console is Error: "Unsupported alert type=notice"

There is very simple workaround, refresh the page and you'll see job invocation detail page. Given the workaround, I don't think that's a blocker

Comment 6 Marek Hulan 2019-08-09 07:01:57 UTC
It works in development env, but I see the same error, here's the trace

Warning: Failed prop type: Invalid prop `type` of value `notice` supplied to `ToastNotification`, expected one of ["error","warning","success","info","danger"].
    in ToastNotification (created by ToastsList)
    in ToastsList (created by Connect(ToastsList))
    in Connect(ToastsList) (created by I18nProviderWrapper(Connect(ToastsList)))
    in IntlProvider (created by I18nProviderWrapper(Connect(ToastsList)))
    in I18nProviderWrapper(Connect(ToastsList)) (created by StoreProvider(I18nProviderWrapper(Connect(ToastsList))))
    in Provider (created by StoreProvider(I18nProviderWrapper(Connect(ToastsList))))
    in StoreProvider(I18nProviderWrapper(Connect(ToastsList)))

Comment 7 Marek Hulan 2019-08-09 07:02:42 UTC
Created redmine issue https://projects.theforeman.org/issues/27566 from this bug

Comment 8 Bryan Kearney 2019-08-19 10:01:48 UTC
Upstream bug assigned to aruzicka

Comment 9 Bryan Kearney 2019-08-19 10:01:50 UTC
Upstream bug assigned to aruzicka

Comment 10 Bryan Kearney 2019-08-20 12:01:52 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27566 has been resolved.

Comment 12 Peter Dragun 2019-08-26 11:20:47 UTC
Verified on Satellite 6.6 snap 17 using steps from problem description on Mozilla 68.0 (64 bit) and Chrome 75.0.3770.142 (Official Build) (64-bit). On both browsers everything works as expected.

Comment 13 Bryan Kearney 2019-10-22 19:51:08 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, 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-2019:3172


Note You need to log in before you can comment on or make changes to this bug.