On Jul 12, 2016, at 11:54 PM, Brent Troge wrote: > can you also run, 'pvscan' on the volume-server and send that output > > does your scheduler even inventory the volume-server ? > > do you see any references to 'free_capacity' in your scheduler logs ?
With _a lot_ of trial and error (and really reading every single character of the debug/log output from a restart and a create), it might have been this: 2016-07-12 23:44:16.711 9199 DEBUG cinder.scheduler.filters.capabilities_filter [req-ae7c0c47-9d08-4d81-a94b-56a4feaf2922 4b0e25c70d2b4ad6ba4c50250f2f0b0b 04ee0e71babe4fd7aa16c3f64a8fca89 - - -] extra_spec requirement 'LVM_iSCSI' does not match 'LVM' _satisfies_extra_specs /usr/lib/python2.7/dist-packages/cinder/scheduler/filters/capabilities_filter.py:59 The "LVM_iSCSI" was part of the '[zol]' driver and there was no "volume_backend_name" set for the '[lvm]' one.. https://github.com/FransUrbo/openstack_bladecenter/commit/63fe97399bdd0a49fcf30dcf670cf40e25b4306c Fixing the config file, I can now create a dummy volume, a volume from an image AND there's the expected "nova" availability zone in Horizon! However, I now (again!) get "Block Device Mapping is Invalid." when trying to create an instance with a volume from an image. The volume is created, but then deleted and instance create fails. I'm going to continue this tomorrow and read the logs for that more closely. Thanx for the help! -- Att inse sin egen betydelse är som att få ett kvalster att fatta att han bara syns i mikroskop - Arne Anka _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
