On Thu, Sep 21, 2017 at 2:29 PM, Vasu Kulkarni <vakulkar@xxxxxxxxxx> wrote: > > > On Thu, Sep 21, 2017 at 2:11 PM, Yuri Weinstein <yweinste@xxxxxxxxxx> wrote: >> Detailed summary of the QE Validation can be found here >> http://tracker.ceph.com/issues/20613#note-65 >> >> rados (subset 227 jobs) >> rbd >> rgw >> fs >> krbd >> kcephfs >> knfs >> rest >> hadoop >> samba >> ceph-deploy >> ceph-disk >> upgrade/client-upgrade >> upgrade/hammer-x (jewel) >> upgrade/jewel-x/point-to-point-x >> powercycle >> ceph-ansible >> (please let me know if any suites are missing from this ^ list) >> >> >> ============================== >> Issues requiring approval/decision: >> >> rados - needs Josh review/approval >> fs - needs Patrick review/approval >> krbd - approved by Ilya >> hadoop - EXCLUDED FROM THIS RELEASE >> samba - EXCLUDED FROM THIS RELEASE >> upgrade/jewel-x/point-to-point-x Nathan is fixing one issue >> ceph-ansible - >> needs Sebastian, Vasu, Andrew review/approval > > Ceph-ansible is green and thats what i told in irc as well > http://pulpito.ceph.com/vasu-2017-09-20_19:51:59-ceph-ansible-jewel-distro-basic-vps/ > (it uses stable-2.1 branch of ceph-ansible) > The failing tests during purge-cluster at the end can be ignored for now. I suspect the backporting team does not know about ceph-ansible PRs to be backported because they look for issues in the tracker and ceph-ansible is not there. https://github.com/ceph/ceph-ansible/issues/1938 Abhishek, Nathan, Vasu, Sebastian ? > >> >> I am not clear on our validation approach for ceph-ansible suite and >> added a ticket to address it >> https://github.com/ceph/ceph-ansible/issues/1938 >> >> Nathan, over after we do minor clean up it feels we will be ready to >> publish v10.2.10. >> >> Thx >> YuriW >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
