Re: [Puppet Users] Correction: Puppet Platform 6.27.1 (not 6.27.0) is now available!

[Michael Hashizume]

Sorry for the confusion on this one. In future releases we'll ensure that
the puppet-agent and puppet versions match, even in edge cases like the one
we encountered in this release.

If I understand your issue Steve, you should be able to specify the
package_version parameter to 6.27.1 with the puppet-agent module to upgrade
your agent:

[root@immodest-roll ~]# rpm -qa | grep puppet-agent
puppet-agent-6.26.0-1.el7.x86_64
[root@immodest-roll ~]# cat manifest.pp
class {'::puppet_agent':
  package_version => '6.27.1',
}
[root@immodest-roll ~]# /opt/puppetlabs/bin/puppet apply manifest.pp
Notice: Compiled catalog for immodest-roll.delivery.puppetlabs.net in
environment production in 0.23 seconds
Notice: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure:
ensure changed '6.26.0-1.el7' to '6.27.1'
Notice: Stopping run after puppet-agent upgrade. Run puppet agent -t or
apply your manifest again to finish the transaction.
Notice: Applied catalog in 12.51 seconds
[root@immodest-roll ~]# rpm -qa | grep puppet-agent
puppet-agent-6.27.1-1.el7.x86_64

*Michael Hashizume*
Software Engineer, Puppet Agent
michael.hashiz...@puppet.com


On Wed, Apr 27, 2022 at 6:07 AM Steve Huston 
wrote:

> On Thu, Apr 21, 2022 at 12:20 PM Josh Cooper  wrote:
> > On Thu, Apr 21, 2022 at 7:32 AM Steve Huston 
> wrote:
> >> Apr 21 10:25:03 coathook puppet-agent[11565]: Starting Puppet client
> >> version 6.27.0
> >> Apr 21 10:26:54 coathook puppet-agent[11569]:
> >> (/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure)
> >> change from '6.27.1-1.el7' to '6.27.0' failed: Could not update:
> >> Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
> >> returned 1: Error: Nothing to do (corrective)
> > This is a bug in the puppet_agent module when using the "auto"
> parameter, see https://tickets.puppetlabs.com/browse/MODULES-11315 You
> can workaround the issue by specifying the desired version explicitly. The
> module assumes the version of the puppet library the compiler is using
> (derived from Puppet::PUPPETVERSION) is the same as the version of the
> puppet-agent package. The versions are usually updated together, but it is
> not always true, as sometimes we update ruby/openssl/curl in the
> puppet-agent package due to CVEs without making changes to the puppet
> library.
>
> But what would I force it to?  6.27.1-1 isn't what the package reports
> internally, so if I force that it'll find it via yum but then complain
> on every run that the installed version is older than it should be,
> then fail when the yum upgrade says it's already installed.  6.27.0
> doesn't exist, so if I manually install 6.27.1-1 everywhere it will
> complain that the installed version is newer than the forced one and
> it can't find the old one to downgrade to.  So far I've just kept it
> at 6.26.0 until they reach parity, I don't see any other way to
> continue to use the puppet_agent module and do otherwise.
>
> Based on the comments on the bug now that weren't there last week, I'm
> guessing I'm not alone in this confusion, and staying at 6.26.0 until
> the assumed 6.27.2 comes out is probably for the best.
>
>
> --
> Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci
>   Princeton University  |ICBM Address: 40.346344   -74.652242
> 345 Lewis Library   |"On my ship, the Rocinante, wheeling through
>   Princeton, NJ   08544 | the galaxies; headed for the heart of Cygnus,
> (267) 793-0852  | headlong into mystery."  -Rush, 'Cygnus X-1'
>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAGdQDTr-hVBXuYeHiM2WxPc6BKP9xvnJ2DXyryn0jtnkxMNFLA%40mail.gmail.com
> .
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CALi7aKZFRLXeKuvtr4yqwTmULbhnS5TCERjHw0aZhb%3DCnbabCQ%40mail.gmail.com.

Re: [Puppet Users] Bolt: How to upload a downloaded file?

[Helmut Rickel]

Hello Martin,

my problem was how to implement this in a plan.  In the meantime, a 
colleague told me to use 
/downloads///  . 
This is fine for me. 

Anyway: Thanks a lot for your answer!!!

Kind regards
Helmut

Martin Alfke schrieb am Mittwoch, 27. April 2022 um 15:30:14 UTC+2:

> Hi,
>
> You can reference the actual path by using pwd:
>
> bolt file upload $(pwd)/inventory.yaml /root/ -t login
>
> Hth,
> Martin
>
>
> On 27. Apr 2022, at 14:24, Helmut Rickel  wrote:
>
> Hello,
> this surely is a beginners question: 
> Using bolt, I want to download a file from one server and upload it to a 
> another server. Problem: The function download_file uses a destination path 
> relative to the project directory, but upload_file needs an absolute source 
> path. How do I get this absolute source path?
>
> Thanks for your help!
>
> Kind regards 
> Helmut
>
> -- 
> 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 puppet-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/de6003ab-cb05-46fb-b22c-c57ce5a07a05n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1ab11490-2ae2-4187-b9a3-56f1ce1e82f2n%40googlegroups.com.

Re: [Puppet Users] Bolt: How to upload a downloaded file?

[Martin Alfke]

Hi,

You can reference the actual path by using pwd:

bolt file upload $(pwd)/inventory.yaml /root/ -t login

Hth,
Martin


> On 27. Apr 2022, at 14:24, Helmut Rickel  wrote:
> 
> Hello,
> this surely is a beginners question: 
> Using bolt, I want to download a file from one server and upload it to a 
> another server. Problem: The function download_file uses a destination path 
> relative to the project directory, but upload_file needs an absolute source 
> path. How do I get this absolute source path?
> 
> Thanks for your help!
> 
> Kind regards 
> Helmut
> 
> -- 
> 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 puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/de6003ab-cb05-46fb-b22c-c57ce5a07a05n%40googlegroups.com
>  
> .

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/632346B0-23CE-4A4E-A83B-550D496706C8%40gmail.com.

Re: [Puppet Users] Correction: Puppet Platform 6.27.1 (not 6.27.0) is now available!

[Steve Huston]

On Thu, Apr 21, 2022 at 12:20 PM Josh Cooper  wrote:
> On Thu, Apr 21, 2022 at 7:32 AM Steve Huston  
> wrote:
>> Apr 21 10:25:03 coathook puppet-agent[11565]: Starting Puppet client
>> version 6.27.0
>> Apr 21 10:26:54 coathook puppet-agent[11569]:
>> (/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure)
>> change from '6.27.1-1.el7' to '6.27.0' failed: Could not update:
>> Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade puppet-agent-6.27.0'
>> returned 1: Error: Nothing to do (corrective)
> This is a bug in the puppet_agent module when using the "auto" parameter, see 
> https://tickets.puppetlabs.com/browse/MODULES-11315 You can workaround the 
> issue by specifying the desired version explicitly. The module assumes the 
> version of the puppet library the compiler is using (derived from 
> Puppet::PUPPETVERSION) is the same as the version of the puppet-agent 
> package. The versions are usually updated together, but it is not always 
> true, as sometimes we update ruby/openssl/curl in the puppet-agent package 
> due to CVEs without making changes to the puppet library.

But what would I force it to?  6.27.1-1 isn't what the package reports
internally, so if I force that it'll find it via yum but then complain
on every run that the installed version is older than it should be,
then fail when the yum upgrade says it's already installed.  6.27.0
doesn't exist, so if I manually install 6.27.1-1 everywhere it will
complain that the installed version is newer than the forced one and
it can't find the old one to downgrade to.  So far I've just kept it
at 6.26.0 until they reach parity, I don't see any other way to
continue to use the puppet_agent module and do otherwise.

Based on the comments on the bug now that weren't there last week, I'm
guessing I'm not alone in this confusion, and staying at 6.26.0 until
the assumed 6.27.2 comes out is probably for the best.


-- 
Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci
  Princeton University  |ICBM Address: 40.346344   -74.652242
345 Lewis Library   |"On my ship, the Rocinante, wheeling through
  Princeton, NJ   08544 | the galaxies; headed for the heart of Cygnus,
(267) 793-0852  | headlong into mystery."  -Rush, 'Cygnus X-1'

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAGdQDTr-hVBXuYeHiM2WxPc6BKP9xvnJ2DXyryn0jtnkxMNFLA%40mail.gmail.com.

[Puppet Users] Bolt: How to upload a downloaded file?

[Helmut Rickel]

Hello,
this surely is a beginners question: 
Using bolt, I want to download a file from one server and upload it to a 
another server. Problem: The function download_file uses a destination path 
relative to the project directory, but upload_file needs an absolute source 
path. How do I get this absolute source path?

Thanks for your help!

Kind regards 
Helmut

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/de6003ab-cb05-46fb-b22c-c57ce5a07a05n%40googlegroups.com.