stack/erp5: Keep backward compatibility with ghost cloudooo instances

 Once the requests to cloudooo software types were removed,
 orphan instances might be kept arround due a lack of implementation
 of garbage collection on slapos proxy.

 This change allows the ghost cloudooo instances, don't fail, until
 the garbage collection implementation be deployed, reducing the
 number of irrelevant failures on resilience after an upgrade.

stack/erp5/buildout.hash.cfg

@@ -66,7 +66,7 @@ md5sum = 0969fbb25b05c02ef3c2d437b2f4e1a0
 
 [template]
 filename = instance.cfg.in
-md5sum = 995b5dd89253b79a9511e8b46e91480c
+md5sum = 330b72acf0752cce5da70b1fcdfac487
 
 [monitor-template-dummy]
 filename = dummy.cfg

stack/erp5/instance.cfg.in

@@ -148,6 +148,20 @@ filename = instance-mariadb.cfg
 extra-context =
     section parameter_dict dynamic-template-mariadb-parameters
 
+# Keep cloudooo section for backward compatibility
+# Once the section is removed, ghost instances will keep failing until
+# garbage collection be implemented.
+[dynamic-template-cloudooo-legacy]
+recipe = collective.recipe.template
+input = inline:[buildout]
+  eggs-directory = ${buildout:eggs-directory}
+  develop-eggs-directory = ${buildout:develop-eggs-directory}
+  offline = true
+  parts =
+
+output = ${directory:directory/instance-cloudoo-legacy.cfg
+mode = 644
+
 # we need this value to be present in a section,
 # for slapos.cookbook:switch-softwaretype to work
 [dynamic-template-jupyter]
@@ -171,3 +185,6 @@ zodb-zeo = dynamic-template-zeo:rendered
 zodb-neo = neo-storage-mysql:rendered
 zope = dynamic-template-zope:rendered
 jupyter = dynamic-template-jupyter:rendered
+
+# Keep cloudooo backward compatibility
+cloudooo = dynamic-template-cloudooo-legacy:output