|
I can confirm this when handling ssh-keys as namevars, which is rather a rather common basic example around the Internet and in several books.
It is very common that this gives you errors on every agent run like:
-
puppet agent -t
Notice: Ignoring --listen on onetime run
Error: Checksumfile /var/lib/puppet/state/state.yaml is corrupt ((/var/lib/puppet/state/state.yaml): could not find expected ':' while scanning a simple key at line 804 column 3); replacing
But those do not really do any harm.
But now I have one host that throws the mentioned error in this ticket. On every puppet run:
puppet --version
2.7.23
puppet agent -t
notice: Ignoring --listen on onetime run
info: Caching catalog for monster.sensano.com
info: Applying configuration version '1420798929'
notice: /Stage[main]/Apt::Update/Exec[apt_update]/returns: executed successfully
notice: Finished catalog run in 14.29 seconds
err: Could not send report: Error 400 on SERVER: (<unknown>): could not find expected ':' while scanning a simple key at line 2262 column 5
Despite the success notice, which turns up on any run, too, I think the puppet agent run works as expected, but the master does not receive any reports which makes the management of this host rather problematic.
Is there anything known how to circumvent if not fix this situation on the master? A workaround?
|
