Verification failed due to Bug 1143986.
The fact that the UI failed, doesn't mean the puppet fails. moving back to ON_QA. It can remain in on_qa but verification blocked, it doesn't need to be pushed back to engineering for a fix.
Rajini, can you, please, comment on it? Not sure if you used latest Staypuft bits for deployment. But you had tested multi-backend cinder functionality. Arkady
I tested StayPuft/OSP5 bits and verified that multibackend cinder support works with LVM and Ceph. If the volume_driver is not specified, it will default to LVMISCSIDriver and it worked fine. This is the staypuft version I tested ruby193-rubygem-staypuft-0.2.6-1.el6ost.noarch
IMO this is not a bug. This is how it was working before for single backend as well. It is a nice to have feature.
From my POV, this feature is not fully ready, so it is not verification failed.
Multi-backend is configured and works with the current settings. Adding the missing driver setting can be split off into another bz for a future version, but does not impact whether this was delivered.
I disagree. The multiple back end is designed with the option that the user can create a volume and set the back end manually, it is part of this feature core elements. Without the type configuration the multiple back end feature is not available to the users/operators as it was designed, thus this bug is not fully fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1350.html