Bug 1606276

Summary: Notification.setRenderedSuccessMessage is not a function on bulk product sync
Product: Red Hat Satellite Reporter: Andrew Kofink <akofink>
Component: RepositoriesAssignee: Jonathon Turel <jturel>
Status: CLOSED ERRATA QA Contact: Ales Dujicek <adujicek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: adujicek, egolov, mhulan, sgraessl, walden
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:02:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Kofink 2018-07-20 19:17:12 UTC
Found in nightly

Reproduce:
1. Content -> Products
2. Select a couple products
3. Select 'Sync Now'

Actual:
JS console error is logged, no success message is displayed

Expected:
The success message is properly rendered

Trace:
<pre>
TypeError: Notification.setRenderedSuccessMessage is not a function
    at success (products.controller.self-70e99c05e036c775980bbc3deb5d64d934b918b539bc449eeabb3ffa58991c6c.js?body=1:99)
    at angular-resource.self-e0c3bb2a962d7c8325d92ad502fa79de62eb0112b20c755f19ef662da180cee2.js?body=1:727
    at processQueue (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:15962)
    at angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:15978
    at Scope.$eval (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:17230)
    at Scope.$digest (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:17046)
    at Scope.$apply (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:17338)
    at done (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:11573)
    at completeRequest (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:11779)
    at XMLHttpRequest.requestLoaded (angular.self-208d6d1bf3c22e113e15f13d5f6b598e8f182e9918a6399862a3c3c8c40f9b23.js?body=1:11712)
</pre>

Comment 1 Andrew Kofink 2018-07-20 19:17:17 UTC
Created from redmine issue https://projects.theforeman.org/issues/23957

Comment 2 Andrew Kofink 2018-07-20 19:17:21 UTC
Upstream bug assigned to jturel

Comment 4 Satellite Program 2018-07-20 20:01:16 UTC
Upstream bug assigned to jturel

Comment 5 Satellite Program 2018-07-20 20:01:19 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23957 has been resolved.

Comment 7 Bryan Kearney 2018-10-16 19: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, 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-2018:2927