[maas] fix working directory for rsyslog configs on snap install

[adam-vest]

---

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?

[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-3445
• And now you can install the packages.

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

[TurboTurtle]

Sanity question - was this always wrong, or has it recently changed? Is there a possible (valid) use case for both and we should try to collect each location, knowing that only one is likely to exist on any given host?

[adam-vest]

Heh, I was wondering if this question would pop up. I'm honestly not sure if it's always been wrong, but I checked against all versions that are shipped in the snap store (which goes back to 2.7), and all of those have the directory named syslog, and not rsyslog. 3.0 is also the oldest version that's supported currently, so while it's certainly possible that this is a legacy naming convention, it would have been on versions that are no longer officially available or supported, going back at least 3 years.

[TurboTurtle]

Works for me as-is then.