Bug #14958
Updated by Alexis Mousset over 5 years ago
We should only do this in rudder 5.0 since we already worked around it in 5.1 This is a template, please edit and remove what is not relevant. I found this bug in Rudder version [Your Version here], on [Distribution here] This bug happens: * During installation of Rudder agent / Rudder server * While running rudder agent on a Node * When using Rudder web interface * When looking at compliance of a Node * When configurations are generated on Rudder Server * When a Nodes applies a configuration Description: You can reproduce it with the following steps: * ... * ... You can workaround this issue by doing likewise: