Bug 845611 - Subscriptions are not current message is confusing for system with insufficient subscriptions
Summary: Subscriptions are not current message is confusing for system with insufficie...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Adam Price
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-03 15:07 UTC by Og Maciel
Modified: 2019-09-26 15:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-12 15:20:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot (133.76 KB, image/png)
2012-08-03 15:07 UTC, Og Maciel
no flags Details
The other screenshot is incorrect, use this one (62.57 KB, image/png)
2012-08-03 15:22 UTC, Og Maciel
no flags Details

Description Og Maciel 2012-08-03 15:07:47 UTC
Created attachment 602148 [details]
Screenshot

Description of problem:

If a system does not have sufficient subscriptions to make it compliant ("green"), we current display the following message in the system's Subscription panel:

Subscriptions are not Current

I'd argue that a better message could be:

"System does not have sufficient subscriptions to make it compliant" but better worded :)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Subscribe a system with multiple cpu sockets
2. Subscribe to products that do not provide enough sockets
3.
  
Actual results:

See screenshot attached

Expected results:

Clear/better message

Additional info:

Comment 1 Og Maciel 2012-08-03 15:11:36 UTC
Version-Release number of selected component (if applicable):
* candlepin-0.5.32-1.el6.noarch
* candlepin-tomcat6-0.5.32-1.el6.noarch
* katello-1.1.2-1.git.2.22b3375.el6_3.noarch
* katello-all-1.1.2-1.git.2.22b3375.el6_3.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.6-1.el6.noarch
* katello-cli-1.1.0-1.git.13.d10e8a3.el6_3.noarch
* katello-cli-common-1.1.0-1.git.13.d10e8a3.el6_3.noarch
* katello-common-1.1.2-1.git.2.22b3375.el6_3.noarch
* katello-configure-1.1.1-1.git.0.3794e67.el6_3.noarch
* katello-glue-candlepin-1.1.2-1.git.2.22b3375.el6_3.noarch
* katello-glue-foreman-1.1.2-1.git.2.22b3375.el6_3.noarch
* katello-glue-pulp-1.1.2-1.git.2.22b3375.el6_3.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-0.2.6-1.el6.noarch
* pulp-1.1.11-1.el6.noarch
* pulp-common-1.1.11-1.el6.noarch
* pulp-selinux-server-1.1.11-1.el6.noarch

Comment 2 Og Maciel 2012-08-03 15:22:07 UTC
Created attachment 602158 [details]
The other screenshot is incorrect, use this one

The other screenshot is incorrect, use this one

Comment 5 Dmitri Dolguikh 2012-09-27 15:55:13 UTC
marking as 'on_qa'

Comment 6 Og Maciel 2012-09-28 21:50:55 UTC
Insufficient Subscriptions are Attached to This System is what shows up now.

Verified using:

* candlepin-0.7.8-1.el6cf.noarch
* candlepin-selinux-0.7.8-1.el6cf.noarch
* candlepin-tomcat6-0.7.8-1.el6cf.noarch
* katello-1.1.12-9.el6cf.noarch
* katello-all-1.1.12-9.el6cf.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.8-1.el6cf.noarch
* katello-cli-1.1.8-5.el6cf.noarch
* katello-cli-common-1.1.8-5.el6cf.noarch
* katello-common-1.1.12-9.el6cf.noarch
* katello-configure-1.1.9-4.el6cf.noarch
* katello-glue-candlepin-1.1.12-9.el6cf.noarch
* katello-glue-pulp-1.1.12-9.el6cf.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.1.1-1.el6cf.noarch
* pulp-1.1.12-1.el6cf.noarch
* pulp-common-1.1.12-1.el6cf.noarch
* pulp-selinux-server-1.1.12-1.el6cf.noarch

Comment 7 James Laska 2012-12-12 15:20:05 UTC
CloudForms-1.1 shipped with katello-1.1.12-22.el6cf, candlepin-0.7.8.1-1.el6cf  and pulp-1.1.14-1.el6cf

Marking this bug CLOSED CURRENTRELEASE.  Please reopen if the problem has not   been addressed in the 1.1 product.

Comment 8 Mike McCune 2013-08-16 18:13:53 UTC
getting rid of 6.0.0 version since that doesn't exist


Note You need to log in before you can comment on or make changes to this bug.