Bug 1532254
| Summary: | Puppet Run via Remote execution fails with error "puppet: command not found" | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | sbadhwar |
| Component: | Puppet | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED DUPLICATE | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.0 | CC: | bbuckingham, ehelms, jhutar, mburgerh, mmccune, omaciel, psuriset, sbadhwar |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-16 14:36:37 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
sbadhwar
2018-01-08 13:43:46 UTC
# which puppet /opt/puppetlabs/bin/puppet # rpm -qa | grep puppet puppet-agent-1.10.7-1.el7sat.x86_64 Did you add a enable-puppet4 = true parameter to your organization/host group/etc? (In reply to Og Maciel from comment #2) > # which puppet > /opt/puppetlabs/bin/puppet > > # rpm -qa | grep puppet > puppet-agent-1.10.7-1.el7sat.x86_64 > > Did you add a enable-puppet4 = true parameter to your organization/host > group/etc? Hello, I don't remember adding any such parameter. Please, is there some information on how to pass the above parameter to either organization or host group? Also, to elaborate on the process followed for the Performance setup: - Enable the Satellite Snap repos from https://ohsnap-satellite6.int.open.paas.redhat.com/releases/6.3.0/snaps/30.0/installation - Enable the Puppet 4 repo on host system - Install Satellite - Did a check of puppet version (puppet agent --version) on satellite Output: 4.10.7 Some more output using rpm -qa | grep puppet ran on Satellite host [root@gprfc018 ~]# rpm -qa | grep puppet gprfc018.sbu.lab.eng.bos.redhat.com-puppet-client-1.0-1.noarch puppet-foreman_scap_client-0.3.16-1.el7sat.noarch pulp-puppet-plugins-2.13.4-3.el7sat.noarch redhat-access-insights-puppet-0.0.9-2.el7sat.noarch python-pulp-puppet-common-2.13.4-3.el7sat.noarch puppet-agent-oauth-0.5.1-2.el7sat.noarch puppetserver-2.8.0-1.el7sat.noarch pulp-puppet-tools-2.13.4-3.el7sat.noarch puppet-agent-1.10.7-1.el7sat.x86_64 puppetlabs-stdlib-4.2.1-1.20140510git08b00d9.el7sat.noarch - Sync Puppet 4 Repos to Satellite - Add Puppet 4 repos to Content View - Setup the Activation Key and HostGroup on Satellite with the Content View - Used bootstrap.py(adapted version for puppet 4) on Content host - Verify puppet version installed on content host (rpm -qa | grep puppet) Output: puppet-agent-1.10.7-1.el7sat.x86_64 - Run remote job from Satellite 6.3 using Job category: Puppet and Job Template: Puppet Run Once Is there something else which also needs to be done before executing the job? Hi sbadhwar You can do it by editing your organization and adding the puppet parameter. If you're using host groups to manage your provisioning, then you can also add the parameter to the host group. Furthermore, info about puppet 4 on satellite 6.3 beta https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html-single/upgrading_and_updating_red_hat_satellite/#upgrade_path (In reply to Og Maciel from comment #6) > Furthermore, info about puppet 4 on satellite 6.3 beta > https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/ > html-single/upgrading_and_updating_red_hat_satellite/#upgrade_path Tried with the option mentioned in the docs, seems to resolve the issue on the setup. :) *** This bug has been marked as a duplicate of bug 1527627 *** |