Forwardport v2022->v2023dev3: Disable fstrim timer and service

Forwardport !529 (merged) and !531 (merged)

After a long investigation it was found that fstrim triggered filesystem error on different boards (but not others of same model).

It was also found that on v2021 fstrim.timer is not enabled due to a bug explaining why this issue was not found in that release.

As an initial fix disable fstrimtimer and service.

This fix is only needed in v2022 since the new version of util-linux landed in -security and on the bootstrap process the previous version is installed and then updated.

apertis-issues#70 (closed)

Signed-off-by: Walter Lozano walter.lozano@collabora.com

ospack-fixedfunction.yaml

@@ -201,6 +201,18 @@ actions:
     description: "Disable e2scrub_reap service by default"
     command: systemctl disable e2scrub_reap
 
+  ## Disable fstrim timer and service since they trigger FS issues
+  ## https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/70
+  - action: run
+    chroot: true
+    description: "Disable fstrim.timer by default"
+    command: systemctl disable fstrim.timer
+
+  - action: run
+    chroot: true
+    description: "Disable fstrim.service by default"
+    command: systemctl disable fstrim.service
+
   - action: run
     chroot: true
     description: "Enable iptables services by default"