Red Hat Bugzilla – Bug 1257746
Display error message when using a subscription account that lacks correct entitlements
Last modified: 2016-09-13 12:21:23 EDT
Description of problem:
As of tech-preview if we use a subscription account which lacks correct entitlements, such as a new access.redhat.com account with _no_ subscriptions, the deployment will not advance past the subscriptions page.
This behavior is correct of not advancing, but we want it to display an error message so the user knows why it is not advancing.
As of tech-preview I see no feedback/message, the webui appears to be hung.
Can you send me credentials of a new access.redhat.com account with no subscriptions so I can use the response. Do you mean that there are no subscription management applications as well and none can be created??
This has been already fixed. Please verify.
I've tried this with a SMA that has no subscriptions, see screenshot, and it allowed me to continue by clicking on the 'Next' button. During the validation phase there were no errors displayed and no errors are on Installation Review page. After clicking the Deploy button, the deployment fails with.
"Product 'Red Hat Enterprise Linux Server' does not exist. Confirm that a manifest containing it has been imported."
So the deployment advanced past the Subscription section and allowed me to proceed and start the actual deployment before failing with above error.
I think it would be nicer to display warning/error message in the subscription section when it's obvious the deployment will fail, thus allowing the user to correct the mistake and try again, as opposed to failing the whole deployment.
Joseph, can we convert this to a RFE?
Created attachment 1172912 [details]
account with no subscriptions
I'm asking for Jesus Rodriguez's help on this BZ.
Re-assigning to myself as it it directly related to the subscription work I'm doing.
Fixed by the subscription validation feature
Verified in 20160809.t.1
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.