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 839670 - RFE - Notifications with id of request that caused it
Summary: RFE - Notifications with id of request that caused it
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
urgent
low
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-12 14:11 UTC by Jeff Weiss
Modified: 2014-11-09 22:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-24 19:31:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jeff Weiss 2012-07-12 14:11:41 UTC
Description of problem:
Currently it is impossible to reliably determine whether an automated test passed.  Example.  

The test is, create an org with a blank name, and verify that an error message pops up saying that is not allowed.

So the automation creates a new org, clicks submit, and there is a notification saying "Sync completed successfully:  foorepo".  

That notification had *nothing* to do with the test, it just happened to pop up at the wrong time.  We know that, but the automation has no way of knowing.  It just knows it was supposed to get a red notification and it got a green one.

Even trying to match the content of the notification doesn't work.  It's impossible for automation to tell the difference between some cryptic error it's never seen before that's caused directly by what it's testing, and some cryptic async error that has nothing to do with what it is testing.

Proposed solution:
Each rest action should return an id somewhere in the HTML, and every notification that results from that action should contain the same id.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Brad Buckingham 2012-08-01 17:45:44 UTC
There is one piece of information available in a notice that is rendered that may be useful if trying to associate a notice with a given action performed by the user.

For each notice, katello stores the 'request_type' and passes it back to the client when the notice is delivered. This request type consists of a combination of the controller (e.g. changesets) and the action (e.g. promote) that is being performed.  When the notice is rendered, it will be included as a class on the notice.  For example:
  <ul class="changesets___promote">

This may help; however, if using this example, we scheduled 3 different promotions and received the notices for all of them at the same time, we would not be able to correlate them, other than to look in to the actual text message that comes back. 

If using the action_type is not sufficient, we can certainly look at other solutions to expand the information stored/returned with a notice.

Comment 5 Tom McKay 2012-10-24 19:31:39 UTC
Testing automation has switched to using javascript to track incoming notices

Comment 6 Mike McCune 2013-08-16 18:08:03 UTC
getting rid of 6.0.0 version since that doesn't exist


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