Red Hat Bugzilla – Bug 648454
Sm gui not getting refreshed with add button
Last modified: 2015-04-23 19:56:41 EDT
Created attachment 456841 [details]
sm gui error
Description of problem:
Version-Release number of selected component (if applicable):
Client : Rhel 6 alpha build with sm version 0.92.6-1
Steps to verify :
Register client A , client B to candlepin using same user id
Invoke sm gui on both client .
Subscribe Client “RHEL alpha Entitlement “ at client A using “ADD” button (Quantity is only 1)
Press Add Button(Already invoked sm gui ) at client B
Expected Result :
“Rhel Alpha entitlement”should not available to subscribe.
Actual Result :
Rhel Alpha entitlement is available to subscribe at client B ( “Sm gui not refreshed with Add Button “)
Getting error message while subscribe
Find the attached error screenshot.
good catch, but I am going to push this to the beta.
Waiting on this until new UI is more complete...
I think that the new GUI refreshes the search in each invocation (in the all subscriptions tab). Can we verify if this is still an issue?
Created attachment 472274 [details]
No free entitlements are available for the pool with id 'ff8080812d5eda84012d5edb96850217'
I believe all of this is working as designed and working correctly in the new subscription-manager-gui. Effectively, the user is attempting to subscribe to a subscription/contract for which there are no more quantities available. As such, the user gets an error dialog as shown in attachment 472274 [details] stating that there are no free entitlements. Moreover the "busy dialog" is working well and the application does not hang. I feel the new gui is working correctly with respect to this defect and should be moved to VERIFIED.
Second opinion firstname.lastname@example.org?
I raised that defect against older UI
Agree with John comment
Moving defect status from ON_QA to Verified as per John comment 6
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.