Disable sensu-client in CI

After CI scenario deployment is finished the container ends in unhealthy
state because sensu-client is not successfully connected to RabbitMQ.
We will need to implement default connection to overcloud RabbitMQ instance
for the service to have this service deployed in CI job.

Change-Id: I1aec0c71a945c06a6d914638b45cae074288a90d
Closes-Bug: #1781108

ci/environments/scenario001-multinode-containers.yaml

@@ -23,7 +23,10 @@ resource_registry:
   OS::TripleO::Tasks::ControllerPostPuppetRestart: ../../extraconfig/tasks/post_puppet_pacemaker_restart.yaml
   #Needs to run scenario001
   OS::TripleO::Services::Fluentd: ../../docker/services/fluentd.yaml
-  OS::TripleO::Services::SensuClient: ../../docker/services/sensu-client.yaml
+  # NOTE(mmagr): We need to disable Sensu client deployment for now as the container health check is based
+  #  on successful RabbitMQ connection, which does not happen in this case. We can enable it again when we
+  #  will implement default connection to overcloud RabbitMQ instance,
+  #OS::TripleO::Services::SensuClient: ../../docker/services/sensu-client.yaml
   # Some infra instances don't pass the ping test but are otherwise working.
   # Since the OVB jobs also test this functionality we can shut it off here.
   OS::TripleO::AllNodes::Validation: ../common/all-nodes-validation-disabled.yaml
@@ -92,7 +95,7 @@ parameter_defaults:
     - OS::TripleO::Services::TripleoPackages
     - OS::TripleO::Services::TripleoFirewall
     - OS::TripleO::Services::Fluentd
-    - OS::TripleO::Services::SensuClient
+    #- OS::TripleO::Services::SensuClient
     - OS::TripleO::Services::Iscsid
 
   ControllerExtraConfig:
@@ -163,9 +166,9 @@ parameter_defaults:
   LoggingServers:
     - host: 127.0.0.1
       port: 24224
-  MonitoringRabbitHost: 127.0.0.1
+  #MonitoringRabbitHost: 127.0.0.1
-  MonitoringRabbitPort: 5676
+  #MonitoringRabbitPort: 5676
-  MonitoringRabbitPassword: sensu
+  #MonitoringRabbitPassword: sensu
   TtyValues:
     - console
     - tty1