Bug 1527627
| Summary: | PATH environment variable need to be updated to use puppet binary located at /opt/puppetlabs/bin/puppet | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Ashish Humbe <ahumbe> |
| Component: | Puppet | Assignee: | Eric Helms <ehelms> |
| Status: | CLOSED ERRATA | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3.0 | CC: | bbuckingham, ehelms, mhulan, sbadhwar |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-21 16:54:17 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: | |||
|
Description
Ashish Humbe
2017-12-19 16:47:15 UTC
This is expected behavior per Puppet [1] given we are not at present customizing. However, given we deliver our own set of RPMs we could symlink this path in the puppet-agent to the location that the normal Puppet 3 binfile would be located. [1] https://puppet.com/docs/puppet/5.3/whered_it_go.html#nix-confdir-is-now-etcpuppetlabspuppet *** Bug 1532254 has been marked as a duplicate of this bug. *** Eric, do you prefer to solve this on packaging level with the symlink? I see that provisioning templates already run puppet using the full path, just the job template to run puppet once relies on puppet agent being globally available - https://github.com/theforeman/community-templates/blob/develop/job_templates/puppet_run_once_-_ssh_default.erb Otherwise users would encounter this problem only when running puppet manually I guess. Marek, We should fix this properly in the REX/provisioning templates upstream because we have no control over the puppet-agent package. Further, when installing puppet-agent on clients, users can log out and log back in and the puppet binary will now be present due to the file that lives in /etc/profile.d/puppet-agent.sh. However, in discussions we thought that providing the symlink would reduce the amount of customer friction or support calls when the puppet command is not found during that initial install phase. If you think this would not be an issue, I can not put the symlink in as we are still fixing this. REX will trigger new shell for each invocation so /etc/profile.d/puppet-agent.sh will fix it there. The problem could only occur if as part of same job user installs agent and runs it without specifying the path. But we do not ship any template like that. Kickstart template already determines the right bin path. If relogin solves the issue reported in comment 0 then I'd suggest closing as not a bug. But if you want to add a symlink to avoid the necessity of relogin, that also works for me. Could you please update the BZ accordingly? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
>
> For information on the advisory, and where to find the updated files, follow the link below.
>
> If the solution does not work for you, open a new bug report.
>
> https://access.redhat.com/errata/RHSA-2018:0336
|