mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1191] Global automation polices aren't applied to Linux agents #734
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#734
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ddkooker2 on GitHub (Jun 25, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1191
Originally assigned to: @sadnub on GitHub.
Server Info (please complete the following information):
Installation Method:
Agent Info (please complete the following information):
Describe the bug
I've assigned some Global Polices for Servers/Workstations under settings -> Global Settings
I've made some monitoring Scripts for windows and for Linux, both are added in the automation policy which is configured under Global Settings, under Windows all checks and tasks are assigned correctly and are showing only Windows Scripts (configured in script manager as platform. However the Linux agents aren't getting any policies from the Global configuration.
I've tested this in 2 different environments (both use the same operating systems as given aboven) and both have the same behavior as described here.
To Reproduce
Steps to reproduce the behavior:
3.1. Under a Windows agent:
3.2. Under a Linux agent:
Expected behavior
What I expect to happen is that the available Linux scripts would be applied on the Linux Agents.
When i manually assign the same Automation Policy to the agent the Linux check scripts show up and are working.
@Zebble commented on GitHub (Aug 11, 2022):
To add to this...
Something changed in at least 0.14.6.
Now none of my Linux agents have any checks applied by a policy listed (I haven't tried manually adding directly to an agent), whether they were added before or after the upgrade.
I also tried the "Clear Cache" trick that worked before for policy issues.
@wh1te909 commented on GitHub (Aug 11, 2022):
the policy stuff hasn't really been reworked yet for multi OS support so for now the workaround is to just use add the checks individually on each linux agent, or create a new site just for linux and apply policy there
@sadnub commented on GitHub (Aug 14, 2022):
You need to make sure the supported platform for those scripts is set to ALL or linux for script checks to apply to Linux agents. Only script checks and ping checks are supported at this time.
@sadnub commented on GitHub (Aug 14, 2022):
I actually was able to track down the issue. This will be in the next release.
Thanks!