rapid-cdn: Relax promise constraint

publish-failsafe-error-promise and promise-key-download-url-ready shall be
less reactive, as otherwise it results with constant problems detection on
the running cluster, by raising tickets. When those promises are less
sensitive it gives time for the cluster to stabilize.

software/rapid-cdn/buildout.hash.cfg

@@ -26,11 +26,11 @@ md5sum = 081aef1b071585e5f334a93d6d4969d0
 
 [profile-master]
 filename = instance-master.cfg.in
-md5sum = 5ded3544de312750d0ae06fdb3a436c9
+md5sum = e1e5ad77f5e4882f06e4d8bab5132393
 
 [profile-slave-list]
 filename = instance-slave-list.cfg.in
-md5sum = 96bd66e98c7b4492ab4aba46e0e14e13
+md5sum = 52b752dbac369a47f3f3114cca411851
 
 [profile-master-publish-slave-information]
 filename = instance-master-publish-slave-information.cfg.in

software/rapid-cdn/instance-master.cfg.in

@@ -1079,6 +1079,11 @@ name = publish-failsafe-error.py
 config-filename = ${check-publish-failsafe-error:file}
 config-state = empty
 config-url = ${check-publish-failsafe-error-publish:url}
+config-failure-amount = 5
+config-result-count = 5
+# It shall bang, as republishing has a chance to fix it, and in order to
+# republish the instance has to reprocess
+config-report-anomaly = False
 
 [buildout]
 extends =

software/rapid-cdn/instance-slave-list.cfg.in

@@ -685,3 +685,6 @@ promise = check_file_state
 name = ${:_buildout_section_name_}.py
 config-filename = ${key-download-url-ready:output}
 config-state = empty
+config-failure-amount = 5
+config-result-count = 5
+config-report-anomaly = True