Steps to reproduce:
1. Deploy a simple env, e.g. 1 controller + 1 compute
2. Rerun task "logging" against a node
# Via Fuel CLI
> fuel node --node-id <node_id> --tasks logging
# or the direct run of the corresponding puppet manifest on a node
> puppet apply --noop /etc/puppet/modules/osnailyfacter/modular/logging/logging.pp
Expected result: no resources are changed.
Actual result: some resources are changed.
Below is the trace of task dry run:
# puppet apply --noop /etc/puppet/modules/osnailyfacter/modular/logging/logging.pp
Notice: Scope(Class[Osnailyfacter::Logging::Logging]): MODULAR: logging/logging.pp
Notice: Compiled catalog for node-3.test.domain.local in environment production in 2.42 seconds
Notice: /Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/49-haproxy.conf]/group: current_value root, should be syslog (noop)
Notice: /etc/rsyslog.d/: Would have triggered 'refresh' from 1 events
Notice: Class[Rsyslog::Config]: Would have triggered 'refresh' from 1 events
Notice: Stage[main]: Would have triggered 'refresh' from 1 events
Notice: Finished catalog run in 2.22 seconds
Description of the environment:
MOS 9.1, snapshot #151
Snapshot details:
UBUNTU_MIRROR_ID=ubuntu-2016-08-03-174238
CENTOS_MIRROR_ID=centos-7.2.1511-2016-05-31-083834
MOS_UBUNTU_MIRROR_ID=9.0-2016-08-17-164322
MOS_CENTOS_OS_MIRROR_ID=os-2016-06-23-135731
MOS_CENTOS_PROPOSED_MIRROR_ID=proposed-2016-08-18-044322
MOS_CENTOS_UPDATES_MIRROR_ID=updates-2016-06-23-135916
MOS_CENTOS_HOLDBACK_MIRROR_ID=holdback-2016-06-23-140047
MOS_CENTOS_HOTFIX_MIRROR_ID=hotfix-2016-07-18-162958
MOS_CENTOS_SECURITY_MIRROR_ID=security-2016-06-23-140002
@Maciej guys, it's a bug in your feature and you had a month to fix it.
Please stop moving bugs right before HCF