[puppet] add 'puppet-agent', 'openvox-agent' and 'openvox-server' to packages

[evgeni]

---

Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

• Is the commit message split over multiple lines and hard-wrapped at 72 characters?
• Is the subject and message clear and concise?
• Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
• Does the commit contain a Signed-off-by: First Lastname [email protected]?
• Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?
• Are all passwords or private data gathered by this PR obfuscated?

[pmoravec]

It would be great if you can squash the two commits into one, but ACK either way.

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/sosreport-sos-4031
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[evgeni]

done

[TurboTurtle]

This would enable the plugin on puppet clients now, when the current version in main does not, correct? Or does the puppet-common package exist on clients? I don't recall off the top of my head.

I don't see anything immediately that raises concerns for me for enabling this on clients, it's just a (potentially) non-trivial change to the targets of this plugin and I want to make sure this is in fact what we want to do.

Code LGTM.

[evgeni]

The old "puppet" and "puppet-common" names were present on clients too. At some point things got renamed to puppet-agent and puppetserver, but never completely updated here. So you could say this re-enables the plugin on clients. :)