This message was deleted.

Maybe by coincidence, but Facter 3 is no longer bundled or tested against Puppet 7. Puppet 6 included both Facter 3 and Facter 4. Puppet 7 switched to using Facter 4 exclusively.

On Arch Linux we build Puppet 7 with facter 3 (and facter team told us that's supposed to work but not officially supported). because facter 4 dropped arch linux support 😞

That's pretty far removed from behavior of the

puppet-agent

package on Windows though.

yeah 😄

our puppet is this

C:\Users\chengkai.liang>puppet --version
6.17.0

ah yeah that's quite old

I assume this is the problem?

mhm

so then we have to upgrade puppet agent or the puppet server

do you have a chance to get a dev machine and install puppet into the default dir and/or use a more modern puppet version?

I can give this a try. but probably will be a little late

that's worth testing before you upgrade all agents 😄

can we use bolt to push new puppet agent?

In general yes

so questsion, if I use bolt to install puppet agent will it upgrade the current agent in the same location or it will moe to c:\program files?

I guess that depends on how you convinced the installer to use that directory

In general, the

puppet-agent

installers are not re-targetable. They will expect to use use

/opt/puppetlabs

or

%SystemDrive%\Program Files

.

so then custom location must be done via msiexec installer

> In general, the

puppet-agent

installers are not re-targetable.

I didn't know that. But it seems my company have it installed in idfferent drive

Looks like there is an

INSTALLDIR

MSI property that can be used on Windows: https://www.puppet.com/docs/pe/2023.5/installing_windows_agents#msi_properties But. Install location is something that I highly recommend not customizing even if there is an option to do so as it always exacts more cost in unexpected broken behavior than it provides in benefit. The inability of the current installation to find

libfacter

during Bolt execution absolutely could be a result of using a non-standard install location.

I understand that. But I didn't take in charge of install agent. This probably already baked into VM image. My point is not to affect current installation location to confuse other team

The docs page I linked above references the Microsoft documentation: https://learn.microsoft.com/en-us/windows/win32/msi/reinstallmode As far as I can tell,

REINSTALLMODE

has no effect on install location. The only difference in the mode string is the

a

flag which re-installs all files in the package vs. the MSI default of

o

which only re-installs files that are missing or at an older version.

thanks for the info. For [String]$install_options = 'REINSTALLMODE="amus"', what I meant is to append INSTALLDIR to it