Description of problem:
This RFE is for supporting Ceph's iSCSI Target in RHEV.
Ceph iSCSI support is being added to RHEL 7.3 in these bugzillas.
We should have support that you can begin testing in early/mid July.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Moving back due to issues found in testing. Waiting for new builds to test.
Moving back to NEW as this is not ready for testing
(In reply to Raz Tamir from comment #16)
> Moving back to NEW as this is not ready for testing
Can you indicate what we're waiting for (and hopefully block this BZ on it) so it's easier to track?
It seems like there's some fix need to be pushed by Mike.
Mike, can you please elaborate why we are blocking here?
(In reply to Raz Tamir from comment #18)
> It seems like there's some fix need to be pushed by Mike.
> Mike, can you please elaborate why we are blocking here?
We were waiting for some patches to get merged in the kernel. They are now merged, but the userspace fixes needed to go with them are not in RHCS 2.3.
I am trying to finish RHCS 3.0 development right now and that will have the fixes. We are hoping to be done next week.
Executed RHV storage smoke automation tests over a seutp with iSCSI domain that reside on Ceph iSCSI server. No issues were found.
iSCSI initiator configuration:
iSCSI server configuration (installed on the Ceph cluster):
** before the last step (disk map to the initiator), the disk creation is missing from the doc. It’s done as follows:
> cd /
> disks/ create pool=rbd size=10
/iscsi-target...age-ge2-vdsm3> auth chap=myserver/mypassword2016
Moving to VERIFIED
The bug is for 4.1.z, not 4.2.0.
Can you repeat the tests on 4.1.z?
Executed the same with 4.1 , no issues were found.
Jenkins execution will be provided offline in mail.
Can you clone this bug to z stream?
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.