Red Hat Bugzilla – Bug 1285434
Validation, Second deployment allows to skip the Subscriptions section (verify entitlements meet need)
Last modified: 2016-09-13 12:23:08 EDT
Second deployment still allows to skip the Subscription section, I can start the deployment with insufficient subscriptions. It then hangs when installing RHEV and waiting for the Data Center to be green.
When I look to Satellite's Content Hosts, I can see the two hypervisors have:
"Subscription Status Fully entitled"
whereas the engine has:
"Subscription Status Fully entitled
Red Hat Cloud Infrastructure, Premium (2-sockets): Guest has not been reported on any host and is using a temporary unmapped guest subscription."
Also Katello Agent reports as not installed on the engine machine.
I believe this is the correct behavior, however there was no verification if the entitlements meet need. There should be some checking in the Subscription section, and an error or at least a warning should be displayed when user tries to proceed without correct entitlements and it is obvious the deployment will fail.
There is relevant bug 1257746 that talks about displaying an error.
John, Jesus, is there a UI issue that I need to look at for this? If so, can you guide me.
The new subscriptions validation will cover this scenario.
* if a new connected deployment, we count the subscriptions required by the deployment. And look at the customer portal for the counts specified in the SMA you associated to the deployment. If it isn't enough we warn you.
* if a new disconnected deployment, we count the subscriptions required by the deployment. And look at the manifest you uploaded for the counts required. If it isn't enough we warn you.
* for subsequent deployments, where a manifest has already been uploaded to the satellite, we count the subscriptions required by the deployment. And look at the satellite for what is available, if it isn't enough we warn you.
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.