task execution ordering is Inconsistent after removing/adding compute node

Bug #1644273 reported by Swann Croiset
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StackLight
New
Undecided
Unassigned

Bug Description

MOS 8 / StackLight plugin 0.10.1

Puppet.log

2016-11-22 23:33:47 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: hiera_override.pp
2016-11-22 23:37:07 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: controller.pp
2016-11-22 23:37:29 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: configure_apt.pp
2016-11-22 23:39:10 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: base.pp
2016-11-22 23:40:08 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: aggregator.pp
2016-11-22 23:40:21 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: configure_afd_filters.pp
2016-11-22 23:40:34 +0000 Scope(Class[main]) (notice): fuel-plugin-lma-collector: cleanup_apt_config.pp

Expected:
the controller.pp manifest must be applied AFTER base.pp

The task dependency is settled here:

https://github.com/openstack/fuel-plugin-lma-collector/blob/stable/0.10/deployment_tasks.yaml#L70

Revision history for this message
Swann Croiset (swann-w) wrote :

There are several consequences:
* Collectd is not configured with appropriate python plugin,
* then no OpenStack metric are collected
* no cluster status computed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.