Whats happening:
When starting gladius-controld with an empty gladius-controld.toml file in the gladius root dir the controld service exits with an error message due to missing configuration options:
$ gladius-controld
2018/09/02 13:33:53 [DEBUG] Using dynamic bind port 35907
2018/09/02 13:33:53 Config.Name field is required.
This configuration was created by the pre 0.6.x installer scripts. If I update from pre 0.6.x I have to manually remove the file.
What do you expect:gladius-controld finds the empty config file - sees that no configuration is given and loads its defined defaults. This behaviour is already implemented in gladius-networkd.
Whats happening: When starting gladius-controld with an empty
gladius-controld.toml
file in the gladius root dir the controld service exits with an error message due to missing configuration options:This configuration was created by the pre 0.6.x installer scripts. If I update from pre 0.6.x I have to manually remove the file.
What do you expect:
gladius-controld
finds the empty config file - sees that no configuration is given and loads its defined defaults. This behaviour is already implemented ingladius-networkd
.Further information: none