stack/monitor: don't enable check-monitor-password-promise yet

when running on test nodes some promise fail because testnode itself has
monitoring and the promise connects to testnode's own monitoring.

This reveals a real problem, but we need to fix testnode first to be able
to use this.

stack/monitor/buildout.hash.cfg

@@ -14,7 +14,7 @@
 # not need these here).
 [monitor2-template]
 filename = instance-monitor.cfg.jinja2.in
-md5sum = b6d264a414fcf286d36f26732e971ca4
+md5sum = 3b0d2c8491f4cd77b4b48157739ef4a2
 
 [monitor-httpd-conf]
 _update_hash_filename_ = templates/monitor-httpd.conf.in

stack/monitor/instance-monitor.cfg.jinja2.in

@@ -414,7 +414,9 @@ depends =
   ${ca-monitor-httpd-service:wrapper-path}
   ${monitor-httpd-promise:name}
   ${monitor-frontend-promise:name}
-  ${check-monitor-password-promise:name}
+# XXX this is not enabled yet because this conflicts with testnode's own
+# monitoring.
+#  ${check-monitor-password-promise:name}
   ${monitor-bootstrap-promise:name}
   ${monitor-symlink:recipe}
   ${promise-check-slapgrid:recipe}