Mcollective module used in Fuel provides string values
to ':order' field of mcollective::*::setting resources,
while fuel::mcollective task also supplies integer values.
In puppet3 that was fine because all values provided
to resources were stringified, but in puppet4 they aren't.
This causes failures of comparison inside datacat_collector
resource used in mcollective module.
Change-Id: I9f3bce1f2e21166d31f0b8213d282a56c2c2482d
Closes-Bug: #1668288
It seems that there are at least two level of ruby-stomp brokenness and
the fact that the mutex in original commit is locked actually means
there is no heartbeat received in time and we need to do something about
this.
This reverts commit 8318d70565.
Partial-Bug: #1644618
Change-Id: I565f430d17bcee2c50c0ddc8ecc11f3dc8b420ed
(cherry picked from commit 13b4d0f38e)
Stomp heartbeat handling is quite poorly designed. It happens in a
separate thread which sleeps, then tries to read a heartbeat if reading
mutex is acquired by message receiving thread it fails and increases
lock failure count. Upon reaching the limit (in our packets it is 2 by
default) it forcibly closes the connetion causing reconnect. Setting the
value to 0 turns the feature off.
Change-Id: Ieec889828d1dd2654ee760e7d5676efd14c7c348
Closes-Bug: #1613246
Closes-Bug: #1298262
This module is a fork of nailgun puppet module with
some simplifications that make it easier to use and
maintain. Fuel master node is to be deployed using
kind of task based procedure when {task}.pp
are used one by one
Implements blueprint: get-rid-docker-containers
Change-Id: I0139cad1c2ebb0cc846c8bca560533b0ac6489cf
Andreas Jaeger