[Feature request]: Windows MSI Package

[Vincent-Cabot]

Use Case

Hi there,
We are currently checking if a migration from puppet to openvox can be feasible and reliable, but I'm not able to find msi package for openvox
The landing page announces Windows support but the install page doesn't
Is it planned for a future release or Windows support will be stopped ?

Describe the solution you would like

Provide a windows installer package for openvox

Describe alternatives you've considered

Depending on availability time for Windows package, I presume that puppet msi package should remain compatible when puppet server will be migrated on openvox, it can be a way until release

Additional context

No response

[bastelfreak]

Hi,
we've beta builds available at https://artifacts.voxpupuli.org/downloads/windows/openvox8/. Feel free to test them and provide feedback.

[DanielTei]

Hi,
Thanks for building the agent, great timing as I'm looking to replace Puppetserver with Openvox. I've installed the agent and it runs without issue.

One thing I noticed though, it's missing the "aio_agent_version" fact, while the Linux version still has it. Would it be possible to re-add it? Asking because I use the forge module "puppet_agent" to upgrade it on my clients, and if that fact is undef, the agent run fails.

And on that note, do you believe it'll still be possible to use that module to easily upgrade the Openvox agents?

Thank you and the team for all your hard work.
Dan

[Vincent-Cabot]

Hi,

Thanks @bastelfreak for the link to release candidates, at the moment it runs correctly

I noticed also a change with openvox, now the installation is in "C:\Program Files\PuppetLabs\Puppet" instead of previous "C:\Program Files\Puppet Labs\Puppet" with puppet 8.10

Thank you for this fork !

[nmburgan]

@Vincent-Cabot The path has been fixed in the latest RC version.

[nmburgan]

@DanielTei The puppet_agent module doesn't work quite right with OpenVox due to some hard coding they have in there. We're recommending people use theforeman-puppet instead.

[dteixeira1-godaddy]

@nmburgan Thanks for the suggestion, will have a look 👍

[dteixeira1-godaddy]

Hi @nmburgan, related to the puppet_agent module, thought I'd post this here as it might help others when migrating from Puppet to Openvox.

When using it for Puppet agent updates, our code looked something like this:
class { 'puppet_agent': package_version => '7.33.0', collection => 'puppet7', package_name => 'puppet-agent', wait_for_puppet_run => 480000, windows_source => 'https://url/to/msi', }

The way the module works, it builds the full url using a few variables, as can be seen in the manifest puppet_agent/manifests/osfamily/windows.pp, in our case, on line 27, which has:

$source = "${puppet_agent::windows_source}/windows/${puppet_agent::collection}/${puppet_agent::package_name}-${puppet_agent::prepare::package_version}-${puppet_agent::arch}.msi"

For us, the variable windows_source didn't change, but we did have to change a couple of others. However, this can be done at runtime, without having to touch the module code. So for this to work (for us of course), all we had to do was, in the manifest we use to deploy software, change a couple of things to the block above. It now reads:

class { 'puppet_agent': package_version => '8.17.0', collection => 'openvox8', package_name => 'openvox-agent', wait_for_puppet_run => 480000, windows_source => 'https://url/to/msi', }

By specifying the variables "package_version", "collection" and "package_name", all we had to do was, in our repository, create the necessary folders to put the MSI in. Once that was done, we were able to once again use this module to deploy the Openvox agent.

Hope this helps.

P.S.: The formatting of the code blocks got messed up, but it's just the standard stuff.

[dteixeira1-godaddy]

Related to the agent installation but thought it'd be better to have a separate post for this. We have just over 1700 clients atm, and deploying the Openvox agent to replace Puppet was, for the vast majority, painless. However, did noticed in maybe 10 or 15 an issue. The install itself was fine, however running the agent after showed this error message:

Info: Refreshing CA certificate
Info: CA certificate is unmodified, using existing CA certificate
Error: Certificate 'CN=servers.fqdn' is revoked
Error: Certificate 'CN=servers.fqdn' is revoked

So not sure why but on those clients, their Puppet cert was revoked. Different OSes, different environments, etc, so haven't spotted a pattern yet. Easy fix of course, delete the client's ssl folder, run the agent so a new cert gets requested and sign it, but thought I'd bring it up in here as it might be an issue somewhere.

Thanks.

[dacron]

Can we get the packages chucked on to Chocolatey?