RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/1634

From review point with ftweedal on original Features feature:

> I think that we should store the config in LDAP so that a change on
> one replica is effected on clones.  Obviously this is a fair bit
> more work I am OK with using CS.cfg initially but we should have
> this discussion.
> 

Agreed that this is something we should discuss.  Part of the reason this is system specific though is that people tend to update one system at a time -- in case something goes wrong.  So you can very easily see a situation where a feature is available on one system but not another.

Still, having it in LDAP would allow doing things like enabling features topology-wide for instance.

Per CS Bug/Ticket Triage held 04/19/2016:  RHEL 7.4

Confirmed with alee and ftweedal:

    I think 10.4/RHEL 7.4 is OK; AFAIK we won't have any features likely
    to be dynamically enabled or disabled during deployment lifecycle.

Per RHEL 7.5.z/7.6/8.0 Triage:

edewata: close RHEL bug, keep upstream ticket in FUTURE