Comment 1 for bug 1955769

Debug logs show that nova-compute is aware of the mounts:
```
2021-12-26 22:39:55.691 7 DEBUG nova.virt.libvirt.volume.mount [req-1fba932d-3dcd-42aa-94a5-91ca99902588 3c4f2250c3004f89be7e905716217274 e5dba6e61405445582de5b930f191606 - default default] _HostMountState.mount(fstype=nfs, export=<NFS_HOST_IP>:/srv/nfs, vol_name=volume-09c2935f-1aa3-4bae-90bc-ae9531302c39, /var/lib/nova/mnt/893cab8cdeb3fe1a058e59540fdd5379, options=[]) generation 0 mount /var/lib/kolla/venv/lib/python3.8/site-packages/nova/virt/libvirt/volume/mount.py:287
```
Within the container, that parent-path does not exist:
```
(nova-compute)[root@<HOSTNAME> /]# ls /var/lib/nova/mnt/893cab8cdeb3fe1a058e59540fdd5379,
ls: cannot access '/var/lib/nova/mnt/893cab8cdeb3fe1a058e59540fdd5379,': No such file or directory

```
so the NFS mount can't be created. Creating that path inside /var/lib/nova/mnt results in it being removed