Description of problem:
Working glance using cinder with iSCSI backends.
Need to be able to use Dell SC, Dell PS and ScaleIO for both cinder and glance thru cinder.
There were still open bugs upstream on it when Ocata started.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It is possible that it is already fixed in Ocata.
Quick update on this on to capture some recent discussion. There should really be no additional iSCSI-backed specific work for this and if the dependent RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1293435 is functional, this should just represent verification on the desired iSCSI backend. We are going to focus on verifying LVM first on for the glance-cinder support (we had tested ceph last time and found issues, but glance has separate ceph support, so we will not be testing it or planning to support RBD in this case). Once LVM is working as a test case, then we can test iSCSI with what's available in house. We do not have one of these particular Dell-EMC backends in house, so I marked this one OtherQA so we don't lost track of that.
Match milestone to https://bugzilla.redhat.com/show_bug.cgi?id=1293435
which is waiting on one fix to merge before we can start testing.
we will need that to be backported to OSP10 (and OSP11 to be able to support upgrade).
Hi arkady, We are currently still trying to make this one function and it is in test. Once we see the extent of the changes we can determine if this is something that can be backported.
I'm going to check to see if we have an OSP-10 RFE/clone for this one where we can track that in either case.
RH OSP 12 RC contents are up on the RH OSP beta channel. This bug is marked as OtherQA. If you can take a look at the packages and content and test this bug to see if it is resolved. It would be much appreciated to get feedback on if this is verified or if there is an issue before we get to GA.
We are currently blocked on OSP12 in the Futureville stamp. Is this something we can use the upstream distribution like RDo and verify?
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.
Thanks, we will verify this in OSP12 when we have a successful deployment. And if there are issues will open a new bug
We are still waiting to test this on OSP12