Hide Forgot
Description of problem: Installation Review displays that there are no subscriptions in manifest even when subscriptions are attached to SMA. Version-Release number of selected component (if applicable): QCI-1.0-RHEL-7-201608125.t.0 How reproducible: 100% Steps to Reproduce: 1. Install/configure QCI 2. Deploy RHV self-hosted 3. At Installation Review, examine Subscriptions > Quantity Actual results: Quantity 0 - no subscriptions in manifest Expected results: Quantity 0 + 20 = some description Additional info:
Please note: The deployment proceeds without error and the display corrects itself after about 50%
Used same account + SMA used to file this, was unable to reproduce. See attachment.
Created attachment 1195452 [details] Correct subscriptions
Verified in QCI-1.0-RHEL-7-20160829.t.0
Dev was able to reproduce this consistently: 1) New deployment, navigate to 3A content provider 2) Sign into account and click next 3) Select an SMA but don't click next, instead click 4.Review in the top bar Actual results: Incorrect quantities and products reported under subscriptions Expected results: Correct subscriptions should be reported. We have a proposed fix but it's potentially destabilizing for 1.0, will implement and test for 1.1
https://github.com/fusor/fusor/pull/1245 The SMA and attached subscription information is saved on the SMA page. You should be able to choose an SMA, click Review, and see the correct attached subscriptions.
Verified in QCI-1.1-RHEL-7-20161011.t.2 Note two things: - what is shown has drastically changed (for the better) such that the original screen shot does not even apply anymore. - there is a new anomaly where it seems to be showing the entitlement data multiple times. I'm going to write a new bugzilla report for that.
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/RHEA-2017:0335