Bug 1125982
Summary: | "Configuration" tab should be available for an organization only in case of Provisioning entitlements are provided. | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Dimitar Yordanov <dyordano> |
Component: | WebUI | Assignee: | Grant Gainey <ggainey> |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 560 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-03 19:57:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 924189 |
Description
Dimitar Yordanov
2014-08-01 14:19:23 UTC
The problem with removing access to the Config tab when an org loses Provisioning, is that it doesn't just remove the ability to do provisioning-things to their systems - it keeps them from accessing the config-files they've set up. This is Rude. Generally, once an org has had access to any of the 'unlockable' functionality, we don't remove it even if they lose the entitlement. Individual systems will no longer be able to BE provisioned, because that's controlled by "do they have the Provisioning entitlement assigned" - but the customer data the user has stored in Satellite should remain available. |