Comment 2 for bug 1825159

Ryan, I do think there is an issue somewhere (hopefully, on my configs).
Just to clarify, I am following the step-by-step as described on: https://jujucharms.com/cinder/

Section "Separate volume units for scale out, using local storage and iSCSI"
Please, double-check juju status --relations to see if all relations on this Section have been applied: https://pastebin.canonical.com/p/v4hdRVHD9H/

Notice that we have cinder-volume (with only volume service) and cinder (with both api and scheduler).

You can see on my bundle that config-flags have been commented out: https://pastebin.canonical.com/p/DD4YhgDTpX/

So, I am now running on what documentation suggests as standard for cinder-volume scaling.

Even on this case, when running LVM, I get the very same error on cinder-volume: https://pastebin.canonical.com/p/4WnrKvKNvp/

I did some searching on the docs and found out a manual on multi-backend: https://docs.openstack.org/cinder/latest/admin/blockstorage-multi-backend.html

Even though applying the steps above as recommended: https://pastebin.canonical.com/p/tkq32ccfgN/, I still see the same error trying to add my volume to the server.

I think the co-location of nova-compute and cinder-volume is causing some issues. I cannot figure out what, exactly.

Notice that on the original bug text I did enable InstanceLocalityFilter. But the issue just pops up later, at cinder-volume. If InstanceLocalityFilter was the reason, I should see Scheduler filtering / not-filtering correctly. The InstanceLocalityFilter seems to be fine.