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.
Description of problem: Puppet module uploaded with incorrect syntax in code is not listed in host -> puppet classes tab. There must be notification message or warning when uploading puppet module with incorrect code.
Version-Release number of selected component (if applicable):6.2.4
How reproducible: Always
Steps to Reproduce:
1. Create a puppet module with incorrect code(like missing ',') in init.pp
2. Upload module to repository and publish content view.
3. Now edit host and try to apply puppet class but the puppet class is missing here.
Actual results: Puppet class is missing
Expected results: There should be warning or notification that few puppet class are hidden due to incorrect syntax.
Additional info:
I don't think Pulp is the right place to do linting or syntax checking on software artifacts. It should definitely do integrity checks when possible, like verifying checksums and sizes. But teaching Pulp how to evaluate Puppet code, Python code, or the domain-specific validity of any content type is far outside the scope of Pulp's role as a manager of repositories.
In other words, garbage-in-garbage-out.
I'm changing the component to Content Management in case someone has an idea of another part of Satellite that makes sense to evaluate and report on this kind of thing.
Maybe if the complaint is that the module is just missing from the Katello UI with no explanation, there's some way for an explanation to be reported?
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.