lassification::pe_node_group_environment
>
> per
> https://puppet.com/docs/pe/2019.8/installing_pe.html#configuration_parameters_and_the_pe.conf_file
>
>
> Good Luck,
>
>
> Mike
> --
> *From:* puppet-users@googlegroups.com on
> behalf of Vinay
server and pe-console services .
>
> Regards,
> Nandha
>
> On Wed, 26 May, 2021, 5:45 pm Vinay Korrapati,
> wrote:
>
>> Hi Team,
>>
>> I have installed the puppet enterprise 2019.8.1 version in my
>> preproduction environment.
>>
>> Later i hav
Hi Team,
I have installed the puppet enterprise 2019.8.1 version in my preproduction
environment.
Later i have created a new environment as : preproduction.
i could observed *production (default) *got missed under
/etc/puppetlabs/code/environments/ .
Hence often its throwing the below
Hi Team,
I would like to invoke a ruby function from the puppet ruby task.
here the example :
I have a module :
Can i call the function1.rb function in
sample.rb task ? (function and task both are in same module) .
And can we call the ruby function (function2.rb) which is under different
puppet enterprise : 2019.8.1
Oracle: 12c
On Friday, January 22, 2021 at 1:10:42 PM UTC+5:30 Vinay Korrapati wrote:
> Hi Team,
>
> Can we pass the credentials in custom facts in secure way?
>
> *Use case : *I have to write a fact which , executes a Query on Oracle
> DB's and
Hi Team,
Can we pass the credentials in custom facts in secure way?
*Use case : *I have to write a fact which , executes a Query on Oracle DB's
and returns the output.
To execute the query it requires the credentials ($oralogin).
Eg:
$OracleUserName="username"
$OraclePassword="password"
Hi Team,
I am unable to retrieve the puppet master FQDN through plans. Below are the
steps taken so far:
1.
$puppet_master_details = run_plan('facts', '*nodes*' => 'localhost')
$puppet_master_results = $puppet_master_details.results
$puppet_master =
our code?
>
> Running plans via PE Console requires that the plan is:
> - deployed within a module to the puppet master
> - is placed into the plans folder of the module
>
> Hth,
> Martin
>
>
> On 5. Nov 2020, at 13:55, Vinay Korrapati wrote:
>
> Hi Team,
>
> c
Hi Team,
currently i am using puppet PE: 2019.8.1 version.
followed the article:
https://puppet.com/docs/pe/2019.8/running_plans_from_the_console_.html
As per the puppet docs: we have to choose the plan which we want to run.
But none of my plans are visible in the section.
Able to run the
Hi Team,
I am facing a weird issue. while running a puppet ruby task, it's not
getting executed (run time: 00:00:00).
*Error:* Finished with exit code 2
I was able to execute the same task with the bolt command without any
issues. Issue Occurs when i trigger the task from console.
Puppet
to run the task it will upload it to the
> remote machine to a temporary directory to execute it. By specifying the
> file in your task metadata, PE will *also* upload the required file
> alongside the task file so it's in a predictable location and can be used
> on the remote system.
Hi Lucy,
Thanks for your response.
I already tried and faced the below issue while loading the file.
`require_relative': cannot load such file --
/opt/puppetlabs/pxp-agent/spool/98/temp_task_5881-56e6-b035-6d66/files/testfile.ps1
Its pointing the different path than the expected one :
Hi Team,
I have a ruby task which calls a .ps1 file on puppet master. As a part of
calling the puppet file i need to define the file path in ruby task.
file_path = "/etc/puppetlabs/code/environments//modules//files/.ps1"
script_params = ""
# execution of the script
cmd_output =
Hi Team,
I are planning to upgrade the Puppet Enterprise version from 2019.1.0 to
2019.8.1 in development environment.
As a part of this upgrade i am checking all the prerequisites and other
stuff as well.
If anyone experienced any issues of your migration , kindly share with me
which helps
do that.
>
> On Tue, Sep 1, 2020 at 9:29 AM Vinay Korrapati wrote:
>
>> Hi Team,
>>
>> Is there any possibility to trigger the puppet task/plan from puppet
>> profile ?
>>
>> Regards
>> Vinay
>>
>> --
>> You received this message
Hi Team,
Is there any possibility to trigger the puppet task/plan from puppet
profile ?
Regards
Vinay
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Team,
Can we have all the puppet rest api's list ?
eg:
https://localhost:8081/pdb/query/v4/nodes/
https://localhost:8081/pdb/query/v4/facts/
Regards
Vinay
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and
Hi Team,
Anyone having idea about how to authenticate puppet API in AZure API
management GW or how to add puppet API's in Azure API management GW?
eg: "https://puppetserver:8081/pdb/query/v4/facts;
Regards
Vinay
--
You received this message because you are subscribed to the Google Groups
Hi KevinR,
Thanks for your comment, but would like to test on one machine initially
and then will move to rest of the agents. But facing script halted and
agent is not getting upgraded.
Regards
Vinay
On Tuesday, July 21, 2020 at 7:33:43 PM UTC+5:30, KevinR wrote:
>
> Hi Vinay,
>
> instead of
Hi All,
My PE successfully upgraded from 2019.1.0 to 2019.5.0 but I am unable to
upgrade my puppet agents (windows) from 2019.1.0 to 2019.5.0.
followed the document:
https://puppet.com/docs/pe/2019.5/upgrading_agents.html
Latest MSI file is available in PE and agent as well (tried by
e_notes_pe.html#resolved_issues_pe_x-5
>
> Since this is Puppet Enterprise, you can reach out to support at
> https://support.puppet.com
>
>
>
> On Thu, Jul 16, 2020, 7:16 AM Vinay Korrapati > wrote:
>
>> Hi Rebecca,
>>
>> Thanks for yo
was changed due to the following reasons and docs may also need to be
> updated.
>
> https://puppet.com/security/cve/CVE-2020-7943/
>
> Regards,
>
> Becca
>
> On Thu, Jul 16, 2020, 6:50 AM Vinay Korrapati > wrote:
>
>> Hi Team,
>>
>> we are unable to a
Hi Team,
we are unable to access the puppet status API after upgrade the PE from
2019.1.0 to 2019.5.0.
uri: http://:8123/status/v1/services
getting: 502 bad gateway.
Port is opened and In PE Console node group, in the
puppet_enterprise::profile::console class,
Hi Team,
We have upgraded the puppet master from 2019.1.0 to 2019.5.0 successfully.
While upgrading the PE agents from 6.4.2 to 6.14.0 we are facing the below
error.
change from false to true failed: Failed previous installation with:
*ScriptHalted*
Source:
tlabs/puppetlabs-azure
>
> You can check documentation at the link mentioned above and verify whether
> this module serves your needs.
>
> Hth,
> Martin
>
> On 13. Jul 2020, at 17:22, Vinay Korrapati wrote:
>
> Hi Team,
>
> Is there any puppet APIs which Integr
Hi Team,
Is there any puppet APIs which Integrate with Azure API Management Gateways.
Or any puppet APIs which we can handle the Azure API management Gateways?
Regards
Vinay
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
Hi Team,
I have upgraded the PE from 2019.1.0 to 2019.5.0. As per the component
versions table 2019.1.0 puppet agents (6.4.2) are compatible with PE
2019.5.0
https://puppet.com/docs/pe/2019.5/component_versions_in_recent_pe_releases.html
Any consequences if i am not upgrade my puppet
ote:
>
>> Hi Team,
>>
>> Is there any way to downgrade the puppet master (other than backup and
>> restore process ) ?
>>
>> Regards
>> Vinay
>>
>>
>> On Thursday, July 2, 2020 at 7:43:43 PM UTC+5:30, Vinay Korrapati wrote:
>>>
>>
Hi Team,
Is there any way to downgrade the puppet master (other than backup and
restore process ) ?
Regards
Vinay
On Thursday, July 2, 2020 at 7:43:43 PM UTC+5:30, Vinay Korrapati wrote:
>
> Hi Marty,
>
> Thanks for your quick response. No packages are available under
> opt/pu
Hi Marty,
Thanks for your quick response. No packages are available under
opt/puppetlabs/server/data/packages/public/(*current/2019.5.0*
)/ubuntu-18.04-amd64-6.16.0.
ubuntu-18.04-amd64-6.14.0 contains all the expected (*2019.5.0*) packages.
Kindly suggest further.
Regards
Vinay
On
Hi Marty,
Thanks for your response. No , we are installed the latest version of
Puppet Enterprise 2019.5.0. Even same we can see from the puppet console.
Post up gradation, unfortunately ran the : sudo apt update && sudo apt
upgrade Which causes to take the PE master infrastructure (agent)
Hi Team,
We have upgrade our PE to 2019.5.0 from 2019.1.0. We could observe the
Puppet console showing the correct version which is 2019.5.0.
But when we ran the puppet --version we are getting the 6.16.0 rather than
6.14.0.
we are unable to downgrade the puppet agent version from 6.16.0 to
l/centos8 =>http://crunchtools.com/why-no-docker/
>
>
> On Tue, 30 Jun 2020 at 14:05, Vinay Korrapati > wrote:
>
>> Hi Team,
>>
>> Can someone suggest on the query.
>>
>> i would like to install the docker on Cent OS 8.1 through puppet. As per
>
its supported 7.0 only.
Kindly suggest the supported forge module/any public repo for cent OS 8.1.
Regards
Vinay
On Monday, June 29, 2020 at 10:54:48 AM UTC+5:30, Vinay Korrapati wrote:
>
> Hi Team,
>
> i would like to install the docker on Cent OS 8.1 through puppet. A
Hi Team,
i would like to install the docker on Cent OS 8.1 through puppet. As per
the https://forge.puppet.com/puppetlabs/docker its supported 7.0 only.
Kindly suggest the supported forge module/any public repo for cent OS 8.1.
Regards
Vinay
--
You received this message because you are
Hi Team,
We are facing the below issue while installing the docker Ubuntu 18.04
using existing puppet forge module. we already added the include 'docker'
to the manifest file. And all dependent modules also installed.
*Error:*
*change from 'absent' to 'present' failed: Could not set 'present'
Hi Team,
We have checked the APT package provider of puppet on UBUNTU machine and
YUM package provided on CentOS through puppet package resource.
Similar way would like to test packages in public repository through puppet
package resource on linux machines.
Kindly share any public repos to
>
>
>
>
>
> *From:* puppet...@googlegroups.com <
> puppet...@googlegroups.com > *On Behalf Of *Vinay Korrapati
> *Sent:* Tuesday, June 16, 2020 6:21 AM
> *To:* Puppet Users >
> *Subject:* [Puppet Users] Upgrade puppet 2019.1.0 to 2019.5
>
>
THis has been taken care
On Wednesday, April 22, 2020 at 10:50:23 PM UTC+5:30, Vinay Korrapati wrote:
>
> Hi Team,
>
> Though i have executed the puppet task successfully. Unable to call the
> plan with my ruby task from console getting the below task:
>
> Error: Task exite
Hi Team,
I have to upgrade my PE from 2019.1.0 to 2019.5. Could you please share
your valuable inputs for my successful up gradation.
what are all the prerequisites ?
what cautions i have to take ?
Regards
Vinay
--
You received this message because you are subscribed to the Google Groups
Hi Team,
Though i have executed the puppet task successfully. Unable to call the
plan with my ruby task from console getting the below task:
Error: Task exited 127:
/usr/bin/env: ‘powershell’: No such file or directory.
>From bolt command process has been started but no progress it has stuck
41 matches
Mail list logo
