software/ors-amarisoft: Remove lte_ue during MME launch, not IMS

software/ors-amarisoft/buildout.hash.cfg

@@ -36,7 +36,7 @@ md5sum = fc59d15a7f7f942951f9e38d7a1cca2c
 
 [template-lte-epc]
 _update_hash_filename_ = instance-epc.jinja2.cfg
-md5sum = 0585b4f8fd42538595e6abb61d07fd93
+md5sum = 27d423b3a065fa00a3cf65228f4b798a
 
 [ue_db.jinja2.cfg]
 filename = config/ue_db.jinja2.cfg

software/ors-amarisoft/instance-epc.jinja2.cfg

@@ -62,7 +62,7 @@ context =
 [lte-ims-service]
 recipe = slapos.cookbook:wrapper
 init = ${ltelogs:rendered} ${directory:log}/ims.log; sleep 1
-command-line = rm -f ${directory:var}/lte_ue.db; {{ mme }}/lteims ${directory:etc}/ims.cfg
+command-line = {{ mme }}/lteims ${directory:etc}/ims.cfg
 wrapper-path = ${directory:service}/lte-ims
 mode = 0775
 pidfile = ${directory:run}/ims.pid
@@ -74,7 +74,9 @@ environment = AMARISOFT_PATH=/opt/amarisoft/.amarisoft
 ### MME
 [lte-mme-service]
 recipe = slapos.cookbook:wrapper
-init = ${ltelogs:rendered} ${directory:log}/mme.log
+# When the machine shutdowns abruptly, lte_ue is not cleaned up which causes
+# amarisoft ltemme to fail. TODO: find a cleaner way to handle this
+init = ${ltelogs:rendered} ${directory:log}/mme.log; rm -f ${directory:var}/lte_ue.db
 command-line = {{ mme }}/ltemme ${directory:etc}/mme.cfg
 wrapper-path = ${directory:service}/lte-mme
 mode = 0775