graphite triggers apache errors in first run

[Chris Ricker]

aio, first puppet apply site.pp, cisco repos

Debug: Exec[reload-apache2](provider=posix): Executing '/etc/init.d/apache2 reload'
Debug: Executing '/etc/init.d/apache2 reload'
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: * Reloading web server apache2
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: *
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: * The apache2 configtest failed. Not doing anything.
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: Output of config test was:
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: AH00534: apache2: Configuration error: More than one MPM loaded.
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: Action 'configtest' failed.
Notice: /Stage[main]/Graphite/Exec[reload-apache2]/returns: The Apache error log may have more information.
Error: /Stage[main]/Graphite/Exec[reload-apache2]: Failed to call refresh: /etc/init.d/apache2 reload returned 1 instead of one of [0]
Error: /Stage[main]/Graphite/Exec[reload-apache2]: /etc/init.d/apache2 reload returned 1 instead of one of [0]
Notice: /Stage[main]/Graphite/File[/var/lib/graphite/graphite.db]/ensure: c

[Chris Ricker (chris-ricker)]

The MPM conflict is sorted by the end of the puppet run and apache restarts then

[Ian Wells (ijw-ubuntu)]

It fails the puppet run, causes some dependencies not to run and rather obviously shouldn't be happening.