Benjamin Merot

It's based on a new type of event report which came with [Puppet 4.6](https://docs.puppet.com/puppet/4.6/release_notes.html#identify-manual-change-corrected-by-puppet), that part at least isn't specific to PE.

You don't need to specify Peer resources when you have them declared as serving your bricks.

Problem is still present in newer Ansible. ```shell ansible [core 2.17.0] config file = None configured module search path = ['/Users/xxx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /Users/xxx/Library/Python/3.11/lib/python/site-packages/ansible ansible collection...

If I list the enabled services in systemd, the services created via generators and “enabled” in Ansible do not show up. So Ansible says one thing but the target host...

@bcoca, the issue isn't so much about generators but about Ansible not reporting an error and giving an incorrect feedback about the state of a systemd service. Yes in the...

It seems somebody also asked to have that aspect [clarified on systemd](https://github.com/systemd/systemd/issues/28006). Having for example: ```ini [Install] WantedBy=multi-user.target default.target ``` Will lead generator to create a symlink in `/run/systemd/generator/default.target.wants/`. But...

Issue isn't limited to archives containing links. The parameters used by CDI when calling `tar` won't work with all PVC/StorageClass and Pod security context due to ownership. It looks like...