It looks like libvirtl service can't load 'bridge' kernel module in time before sysctl::vlaue puppet resource tries to execute 'sysctl -w' commands. Which is fine, since it still sets correct values in /etc/sysctl.conf and bridge module sets those keys to '1' itself. So this bug does not break or affect deployment, it just generates those error message in the puppet log. Although it's absolutely safe to ignore those error message from puppet, we still can avoid them if we simply update /etc/sysctl.conf and let 'bridge' module to handle runtime sysctl keys. I've committed appropriate patches to stable/5.1, stable/6.0 and master branches already.
It looks like libvirtl service can't load 'bridge' kernel module in time before sysctl::vlaue puppet resource tries to execute 'sysctl -w' commands. Which is fine, since it still sets correct values in /etc/sysctl.conf and bridge module sets those keys to '1' itself. So this bug does not break or affect deployment, it just generates those error message in the puppet log. Although it's absolutely safe to ignore those error message from puppet, we still can avoid them if we simply update /etc/sysctl.conf and let 'bridge' module to handle runtime sysctl keys. I've committed appropriate patches to stable/5.1, stable/6.0 and master branches already.