From: Krzysztof B. <kb...@un...> - 2021-08-19 10:28:20
|
Hi Sander, W dniu 19.08.2021 o 08:32, Sander Apweiler pisze: > Good morning Krzysztof, all, > > we encountered a problem with configuration loss after restarts. We are > using the configuration files everywhere where it is possible because > we are using puppet as configuration management service. > > The configuration loss we encountered is e.g. > - attached attribute classes > - attribute statements > > If there is a large timeframe between changes and restart, they are > kept. So it is difficult to reproduce this problem. That sounds as a very serious problem, however doesn't ring any bell. Attribute classes and statements as attached to groups can be only stored to and loaded from DB. So I don't think that configuration files matter here. There is also no write-cache that could trigger such situation. I would be less confident in case of objects that are stored in DB but can be also reloaded from config files, but that's not the case here. I'd investigate whether perhaps you have some DB migration policy which looses some data written recently? Or maybe some of the data (e.g. groups) are re-initialized on each restart with either groovy script or via REST? In such case bugs in such automation may overwrite what is in DB. HTHm Krzysztof |