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.

Bug 1595306

Summary: Subscription updates provide no feedback/notifications
Product: Red Hat Satellite Reporter: jcallaha
Component: Subscription ManagementAssignee: Amir <afeferku>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: ehelms, walden
Target Milestone: 6.4.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/23750
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.7-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:15:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
no notification none

Description jcallaha 2018-06-26 14:54:00 UTC
Created attachment 1454688 [details]
no notification

Description of problem:
When making updates to a subscription's entitlement count, there are no task notifications presented to the user. This makes it seem like no action has been taken. Additionally, if the user tries again to make a change, while the original task is running, they will be shown a task conflict warning.

Version-Release number of selected component (if applicable):
Satellite 6.4 Snap 9

How reproducible:
always

Steps to Reproduce:
1. Upload a manifest with subscriptions
2. Navigate to the subscriptions page
3. Update the entitlement count of a subscription.

Actual results:
No feedback is given to the status of the task, and a user can continue to try to make changes, while the previous task is still running.

Expected results:
Some kind of feedback is presented letting the user know that the task is ongoing and then complete. Additionally, the user shouldn't be allowed to make additional changes while the previous task is running.

Additional info:
See attached webm

Comment 2 Walden Raines 2018-06-29 20:31:46 UTC
Connecting redmine issue http://projects.theforeman.org/issues/23750 from this bug

Comment 4 jcallaha 2018-07-30 17:31:58 UTC
Verified in Satellite 6.4 Snap 14.

I followed the verification steps outlined in my initial comment. Now, when updating a subscription entitlement count, a task notification pops up. Additionally, a task progress modal appears on top of a grayed out subscriptions page, stopping the user from editing the form until it completes.

See attached video for verification process.

Comment 6 Bryan Kearney 2018-10-16 19:15:43 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