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).
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.
Ryan, I do think there is an issue somewhere (hopefully, on my configs). /jujucharms. com/cinder/
Just to clarify, I am following the step-by-step as described on: https:/
Section "Separate volume units for scale out, using local storage and iSCSI" /pastebin. canonical. com/p/v4hdRVHD9 H/
Please, double-check juju status --relations to see if all relations on this Section have been applied: https:/
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/DD4YhgDTp X/
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/4WnrKvKNv p/
I did some searching on the docs and found out a manual on multi-backend: https:/ /docs.openstack .org/cinder/ latest/ admin/blockstor age-multi- backend. html
Even though applying the steps above as recommended: https:/ /pastebin. canonical. com/p/tkq32ccfg N/, 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 InstanceLocalit yFilter. But the issue just pops up later, at cinder-volume. If InstanceLocalit yFilter was the reason, I should see Scheduler filtering / not-filtering correctly. The InstanceLocalit yFilter seems to be fine.