Icinga(web)2 deletes roles

UPDATE:
I have found out that roles are deleted by puppet which deploys configs for each server and also administrates Icinga2 through the corresponding puppet module.
Therefore the roles have to be defined in a puppet config file.

Hello everybody,
I want to set up an Icingaweb2 Interface on a local computer + monitor combination that has “viewing” access but cannot edit settings about hosts etc.
I created a new role, group and user as an admin in Icingaweb2 and logged in with the new user on the web interface.
First I can see all the information without being able to edit basic functions, which is what I want.

Once I log out and log back in, the user doesn’t have any rights at all anymore and cannot access the dashboard or a single host and it’s services.
If I log in as an admin, I can see, that the user and the group persist, but the role that is responsible for controlling the access is being deleted regularly.

Is there a reason why this is happening? It seems that the functions already exist for an exact use case like mine but something goes wrong. Where do I look for a solution?
I haven’t found anything in the log files on the master server, where the web interface and the database are running.
Is it a permission thing?

The roles have been deleted due to puppet runs.

2 Likes