-
Notifications
You must be signed in to change notification settings - Fork 5.6k
beacons.enable_beacon does not write to beacons.conf on some OS's #31516
Copy link
Copy link
Open
Labels
Execution-ModuleP2Priority 2Priority 2PlatformRelates to OS, containers, platform-based utilities like FS, system based appsRelates to OS, containers, platform-based utilities like FS, system based appsbugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behaviorseverity-medium3rd level, incorrect or bad functionality, confusing and lacks a work around3rd level, incorrect or bad functionality, confusing and lacks a work aroundstale
Milestone
Metadata
Metadata
Assignees
Labels
Execution-ModuleP2Priority 2Priority 2PlatformRelates to OS, containers, platform-based utilities like FS, system based appsRelates to OS, containers, platform-based utilities like FS, system based appsbugbroken, incorrect, or confusing behaviorbroken, incorrect, or confusing behaviorseverity-medium3rd level, incorrect or bad functionality, confusing and lacks a work around3rd level, incorrect or bad functionality, confusing and lacks a work aroundstale
Type
Fields
Give feedbackNo fields configured for issues without a type.
Expected Behavior
Running
beacons.enable_beacon <beacon>then saving the beacon withbeacons.saveshould write enabled: True to the beacons.conf fileExpected beacons.conf after the save should be similar to this:
Actual Behavior
Saving an enabled beacon does not write to the beacons.conf. I've seen this on Ubuntu 12.04, CentOS 5/6, and Fedora 22.
Steps to Reproduce Issue
On the master:
On the minion:
cat /etc/salt/minion.d/beacons.conf beacons: enabled: true ps: apache2: stoppedVersions Report
Master version report:
Minion version report:
This is also happening on 2015.5.8/9