DLPX-75089 Upgrade verification should not enable nfs services

Author: Prakash Surya

files/common/lib/systemd/system/nfs-mountd.service.d/override.conf

@@ -0,0 +1,10 @@
+[Unit]
+#
+# During upgrade verification, the root filesystem will be booted as a
+# container using systemd-nspawn. When this service runs in this
+# container, it can cause corruption of the NFS volumes on the client
+# (due to us allowing all capabilities to the container).  Thus, to
+# workaround this problem, we explicitly disable this service from
+# running when inside of the container.
+#
+ConditionVirtualization=!container

files/common/lib/systemd/system/nfs-server.service.d/override.conf

@@ -0,0 +1,10 @@
+[Unit]
+#
+# During upgrade verification, the root filesystem will be booted as a
+# container using systemd-nspawn. When this service runs in this
+# container, it can cause corruption of the NFS volumes on the client
+# (due to us allowing all capabilities to the container).  Thus, to
+# workaround this problem, we explicitly disable this service from
+# running when inside of the container.
+#
+ConditionVirtualization=!container

files/common/lib/systemd/system/rpc-statd-notify.service.d/override.conf

@@ -0,0 +1,10 @@
+[Unit]
+#
+# During upgrade verification, the root filesystem will be booted as a
+# container using systemd-nspawn. When this service runs in this
+# container, it can cause corruption of the NFS volumes on the client
+# (due to us allowing all capabilities to the container).  Thus, to
+# workaround this problem, we explicitly disable this service from
+# running when inside of the container.
+#
+ConditionVirtualization=!container

files/common/lib/systemd/system/rpc-statd.service.d/override.conf

@@ -0,0 +1,10 @@
+[Unit]
+#
+# During upgrade verification, the root filesystem will be booted as a
+# container using systemd-nspawn. When this service runs in this
+# container, it can cause corruption of the NFS volumes on the client
+# (due to us allowing all capabilities to the container).  Thus, to
+# workaround this problem, we explicitly disable this service from
+# running when inside of the container.
+#
+ConditionVirtualization=!container