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 968346 - Popup unreliable for "changesets__promote"
Summary: Popup unreliable for "changesets__promote"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-29 13:49 UTC by Kedar Bidarkar
Modified: 2023-09-14 01:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-11 18:54:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kedar Bidarkar 2013-05-29 13:49:00 UTC 
Description of problem:

We have no popup for "changesets__promote".

But from UI under user Notification, we do get a notification for "Successfully promoted changeset "

Tue, 28 May 2013 13:08:40 +0000 success ACME_Corporation Successfully promoted changeset 'create_dev_changeset1113'.
Tue, 28 May 2013 13:08:14 +0000 success ACME_Corporation Started content promotion to Development environment using 'create_dev_changeset1113'
Tue, 28 May 2013 13:07:56 +0000 success ACME_Corporation Promotion Changeset 'create_dev_changeset1113' was created. 

Version-Release number of selected component (if applicable):
[root@XYZ ~]# rpm -qav | grep -i katello 
katello-qpid-client-key-pair-1.0-1.noarch
katello-1.4.2-1.git.469.ba512a5.el6.noarch
katello-cli-1.4.2-1.git.71.2a2d883.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-common-1.4.2-1.git.71.2a2d883.el6.noarch
katello-common-1.4.2-1.git.469.ba512a5.el6.noarch
katello-selinux-1.4.3-1.git.3.ce8227b.el6.noarch
katello-all-1.4.2-1.git.469.ba512a5.el6.noarch
katello-certs-tools-1.4.2-1.el6.noarch
katello-glue-candlepin-1.4.2-1.git.469.ba512a5.el6.noarch
katello-configure-1.4.3-1.git.41.e1043b5.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-glue-elasticsearch-1.4.2-1.git.469.ba512a5.el6.noarch
katello-glue-pulp-1.4.2-1.git.469.ba512a5.el6.noarch
signo-katello-0.0.9-1.el6.noarch
katello-repos-1.4.2-1.el6.noarch


How reproducible:


Steps to Reproduce:
1. sync the fake custom repo
2. Add the content to CS
3. promote the CS
4. we do get popup for 
a) changesets_create
b) changesets_apply
c) but none/unreliable for changesets_promote even thoguh it's a success.
d) Also we do get a notification on dashboard->User Notification

Actual results:
no popup

Expected results:
popup for changesets_promote needs to be reliable.

To be clear, very rarely we get a popup when changeset promotion is a success

Additional info:
Comment 1 Brad Buckingham 2013-05-29 19:38:40 UTC 
Do you also see it missing from the 'notifications' page?

Is it possible that you have multiple browsers or tabs open for the user?  

With those particular notifications, they are delivered asynchronously.  By that, it means that the first browser instance that polls for the notification will get it.  Those polls occur by default every 120 seconds or when the user browses to a new page.  Since this is a success notification, it will be displayed for only a few seconds and then fade away, so it is possible that it happened and it was missed.
Comment 2 Mike McCune 2013-05-29 22:35:28 UTC 
if this is indeed a case of multiple browser windows open, please close
Comment 4 Jeff Weiss 2013-06-17 14:44:23 UTC 
No, we are well aware of the "multiple sessions for the same user" issue and we deliberately user a different user for each session to avoid it.
Comment 5 Bryan Kearney 2014-03-11 18:54:09 UTC 
Closing old bugs which are not relevant based on new UI and CLI
Comment 6 Bryan Kearney 2014-03-12 22:52:55 UTC 
Closing old bugs which are not relevant based on new UI and CLI
Comment 7 Red Hat Bugzilla 2023-09-14 01:44:41 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.