Assuming the above is true, I think that means the LVM setup is pretty much completely unopinionated in your env. Some package is pulling in the LVM package as a dependency, or OSA is dropping LVM mistakenly when it doesn't actually need it, but regardless the lvm.conf should be vanilla on those hosts, right? As in, OSA is not the compute host LVM config at all. If that is true then I think it would be something you could simply manage in your environment with the settings appropriate for your host and expect OSA not to clobber them since it should not take any interest in your LVM config if Openstack is not configured to use LVM.
Even on your host where the nova-compute + cinder-volume are collocated, I think the os_cinder LVM setup stuff won't bite us there because the template should only be dropped if the LVM backend is in use (conditional here: https:/ /github. com/openstack/ openstack- ansible- os_cinder/ blob/9549dd0a91 395b976a1c518e0 f77d4e70b9a7aa6 /tasks/ main.yml# L69-L71)
Assuming the above is true, I think that means the LVM setup is pretty much completely unopinionated in your env. Some package is pulling in the LVM package as a dependency, or OSA is dropping LVM mistakenly when it doesn't actually need it, but regardless the lvm.conf should be vanilla on those hosts, right? As in, OSA is not the compute host LVM config at all. If that is true then I think it would be something you could simply manage in your environment with the settings appropriate for your host and expect OSA not to clobber them since it should not take any interest in your LVM config if Openstack is not configured to use LVM.