monitor_only (non-root) mode of client cannot be reversed by setting to false

Bug #894081 reported by David Britton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
Low
Unassigned

Bug Description

If you try and set monitor_only = false in /etc/landscape/client.conf (reverse of monitor_only = true), monitor_only mode is not reversed. Only deleting the key gets rid of it.

If this needs to be set to "None", or empty string or something, the non-root documentation should be updated appropriately, and we probably should used "monitor_only = true" as the enablement string.

Revision history for this message
🤖 Landscape Builder (landscape-builder) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status: New → Invalid
Changed in landscape-client:
status: Invalid → Triaged
Revision history for this message
Andrew Stok (andrew-stok) wrote :

Mitch Burton has verified that this is still happening.

Changed in landscape-client:
status: Triaged → Confirmed
Changed in landscape-client:
status: Confirmed → Fix Committed
Revision history for this message
Andrew Stok (andrew-stok) wrote :

Completed in Pulse 2024#24. In the self-hosted beta release for this pulse.

Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.