This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2119303 - installer sometimes loads modules from /etc/puppetlabs, breaking execution
Summary: installer sometimes loads modules from /etc/puppetlabs, breaking execution
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Ewoud Kohl van Wijngaarden
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-18 08:58 UTC by Evgeni Golov
Modified: 2024-06-06 12:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:26:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31022 0 Normal Ready For Testing Puppet package ensure in pre hook is not isolated 2022-08-18 09:57:31 UTC
Red Hat Issue Tracker   SAT-12286 0 None Migrated None 2024-06-06 12:26:00 UTC

Description Evgeni Golov 2022-08-18 08:58:34 UTC 
Description of problem:
For reasons unknown to me, a user had a broken puppet-lvm module in /etc/puppetlabs/code/modules/puppetlabs-lvm/, which resulted in the following error when Puppet tried to load it:
Error: Could not run: cannot load such file -- puppet_x/lvm/output

Such a local issue should not have an effect on the execution of the Installer (as it should not load random modules from /etc/puppetlabs, those could be incompatible with the contents of the installer).

Kafo, when running Puppet, does generate a custom configuration to avoid this problem:
# cat /tmp/kafo_installation20220818-28102-108x1gp/puppet.conf
[main]
basemodulepath = /usr/share/foreman-installer/modules:/usr/share/gems/gems/kafo-6.4.0/lib/kafo/../..//modules
color = false
environmentpath = /tmp/kafo_installation20220818-28102-108x1gp/environments
evaltrace = true
factpath = /tmp/kafo_installation20220818-28102-108x1gp/facts
hiera_config = /usr/share/foreman-installer/config/foreman-hiera.yaml
noop = false
profile = false
reports = 
show_diff = true

However, we also have a `apply_puppet_code` function in our hooks (https://github.com/theforeman/foreman-installer/blob/43067e91db3439d662adad313ac43853b4cf0992/hooks/boot/01-kafo-hook-extensions.rb#L34-L37) which does _NOT_ pass a custom config and thus loads the global one from /etc, which DOES read the modules and explodes.

This results in the following error when the installer is executed:
2022-08-18 10:17:51 [ERROR ] [root] Failed to ensure rh-postgresql12-postgresql-server, rh-redis5-redis, foreman-selinux, katello-selinux, candlepin-selinux, pulpcore-selinux are installed
2022-08-18 10:17:51 [ERROR ] [root] Error: Could not run: cannot load such file -- puppet_x/lvm/output
Failed to ensure rh-postgresql12-postgresql-server, rh-redis5-redis, foreman-selinux, katello-selinux, candlepin-selinux, pulpcore-selinux are installed
Error: Could not run: cannot load such file -- puppet_x/lvm/output

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

How reproducible:
100%

Steps to Reproduce:
1. break some auto-loaded code in /etc/puppetlabs/code
2. run installer

Actual results:
Installer fails

Expected results:
Installer succeeds

Additional info:
Comment 1 Bryan Kearney 2022-08-18 12:05:21 UTC 
Upstream bug assigned to ekohlvan
Comment 2 Bryan Kearney 2022-08-18 12:05:23 UTC 
Upstream bug assigned to ekohlvan
Comment 6 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 8 Eric Helms 2024-06-06 12:26:02 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.