Comment 2 for bug 1645624

I was able to reproduce this on 9.x.

I'd like to notice that changing of global_filter option during deployment is more a feature than a bug fix, because it is very user-specific:

- local disks on compute could be named in different way (sd*, vd*, hd* and so on)

- it is impossible to predict which devices end-user wants to mount to the compute node - what if he wants to mount some devices with filtered name which contains LVs, PVs inside?

So in order to fix this we need at least investigate how to differentiate volumes mounted for guests from other volumes and as better solution we need also to make the global_filter configurable by end-user.

So I would suggest to describe this as known issue in documentation and describe a workaround for it.