I'm not setting any values in debconf, I'm only installing the package
(non-interactive) and doing configuration in puppet also.
You are right that puppet will re-enforce our configuration, however, we are
not using the puppet agent, so resetting the value might take up to a few
weeks, depending
As you can read in the first posting, I simply installed it with puppet.
Doesn't seem like such a rare scenario to me. I think any company with a
substantial amount of servers should be using some form of configuration
management. I think any completely non-interactive installation method
will end
Today I had to install postfix again, but manually (entering apt-get install on
commandline) and saw in the console output the following lines:
setting inet_interfaces: loopback-only
This reminded me of this issue and gave me a clue where the problem is.
I think the problem is not directly with d
Even though I have the suspicion it is caused by not doing debconf (as puppet
does not ask questions, but just installs with default values), I too can't
reproduce it on a test-VM with the exact same debconf values as one of our
servers.
I have no idea what puppet does to cause this behavior and
If this is any help, here is the installation log
(/var/log/apt/history.log) from the package upgrade that changed the
config file:
Start-Date: 2012-07-20 06:39:28
Commandline: apt-get -qq -y upgrade
Upgrade: postfix:amd64 (2.9.1-5, 2.9.3-2~12.04.1)
End-Date: 2012-07-20 06:39:31
This is not an
It should be easy to reproduce this. Simply installing postfix on a
fresh server installation in the background (so without any use
interaction) and then chenging the configuration file should do it.
Puppet does nothing special with the package. Also, it uses aptitude to
install it, if that makes a
