Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Created attachment 1009180[details]
Activation keys bug
Description of problem:
When publishing a content view which includes puppet modules the puppet modules are available regardless of the setting (enabled ? Yes/No) in the activation key.
Version-Release number of selected component (if applicable): 6.0.8
How reproducible:
Push a content view with puppet modules and create a new activation key. In the product view you will be able to choose enabled? Yes/No for your puppet modules. This setting doesn't matter because you already pushed your modules. Puppet doesn't care about the Yes or No in the activation key.
Steps to Reproduce:
1. Create a content view with rpms and puppet modules
2. promote it into whatever environment you like
3. Create an activation key
3. In the Product Content tab you can now choose (enabled? Yes/No) for your puppetmodules. The setting is irrelevant.
Actual results:
The setting doesn't matter (Yes or No ) both enable the module
Expected results:
Not sure what to expect as I don't thin your going to be able to set a puppet manifest filter based on keys.
Additional info:
None
Comment 1RHEL Program Management
2015-03-31 17:43:15 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
This bz has been moved to an upstream issue. We will no longer be tracking this in the downstream. When the upstream issue is fixed, the next release of Satellite will include the fix. If this is a concern, please reach out to Bryan Kearney or Rich Jerrido. Thank you.
Created attachment 1009180 [details] Activation keys bug Description of problem: When publishing a content view which includes puppet modules the puppet modules are available regardless of the setting (enabled ? Yes/No) in the activation key. Version-Release number of selected component (if applicable): 6.0.8 How reproducible: Push a content view with puppet modules and create a new activation key. In the product view you will be able to choose enabled? Yes/No for your puppet modules. This setting doesn't matter because you already pushed your modules. Puppet doesn't care about the Yes or No in the activation key. Steps to Reproduce: 1. Create a content view with rpms and puppet modules 2. promote it into whatever environment you like 3. Create an activation key 3. In the Product Content tab you can now choose (enabled? Yes/No) for your puppetmodules. The setting is irrelevant. Actual results: The setting doesn't matter (Yes or No ) both enable the module Expected results: Not sure what to expect as I don't thin your going to be able to set a puppet manifest filter based on keys. Additional info: None