Open alxwr opened 3 years ago
The inspec is not run by the pipeline because no platform is enable in .gitlab-ci.yml
.
@alxwr Ran this locally to see what's preventing the service from running and this is what I've found (using journalctl -xe
):
icinga2[6551]: [] critical/config: Error: Validation failed for object 'alice' of type 'User'; Attribute 'groups': Object
icinga2[6551]: Location: in /etc/icinga2/conf.d/users/alice.conf: 4:3-4:29
icinga2[6551]: /etc/icinga2/conf.d/users/alice.conf(2): object User "alice" {
icinga2[6551]: /etc/icinga2/conf.d/users/alice.conf(3): email = "alice@example.test"
icinga2[6551]: /etc/icinga2/conf.d/users/alice.conf(4): groups = [ "icingaadmins" ]
icinga2[6551]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
icinga2[6551]: /etc/icinga2/conf.d/users/alice.conf(5): vars.jabber = "alice@jabber.example.test"
icinga2[6551]: /etc/icinga2/conf.d/users/alice.conf(6): }
icinga2[6551]: [] critical/config: 1 error
icinga2[6551]: [] critical/cli: Config validation failed. Re-run with 'icinga2 daemon -C' after fixing the config.
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
None.
Describe the changes you're proposing
Under FreeBSD 12, the package for Icinga 2.12.3
users.conf
contains a user group (icingaadmins
) which interferes with commonly used config. Removing this unmanaged file resolves this conflict.Pillar / config required to test the proposed changes
None.
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context