this was the run yesterday http://pulpito.ceph.com/teuthology-2018-05-20_23:11:47-upgrade:luminous-x-mimic-distro-basic-ovh/ On Mon, May 21, 2018 at 6:45 AM, Sage Weil <sweil@xxxxxxxxxx> wrote: > On Mon, 21 May 2018, Jason Dillaman wrote: >> On Mon, May 21, 2018 at 8:29 AM, Jason Dillaman <jdillama@xxxxxxxxxx> wrote: >> > On Sun, May 20, 2018 at 10:42 PM, Sage Weil <sweil@xxxxxxxxxx> wrote: >> >> There are 2 failures that are turning most of the upgrade/luminous-x -> >> >> mimic upgrade tests red: >> >> >> >> - http://tracker.ceph.com/issues/24182 >> >> (rbd/test_librbd_python.sh failure on that feature bit test.. Jason, can >> >> you take a look) >> >> It looks like you ran the test using a luminous branch from your >> personal repo (which is ~3000 commits behind ceph:luminous): >> >> > 2018-05-18T20:44:09.237 INFO:teuthology.orchestra.run.ovh077:Running: 'rm -rf /home/ubuntu/cephtest/clone.client.0 && git clone --depth 1 --branch luminous https://github.com/liewegas/ceph /home/ubuntu/cephtest/clone.client.0 && cd /home/ubuntu/cephtest/clone.client.0' >> >> The fix for this test failure should already be in the up-to-date >> luminous branch. > > Yep, my bad... thanks! > > sage > > >> >> >> - http://tracker.ceph.com/issues/24184 >> >> (swift ./bootstrap is failing with a missing package, libev-devel or >> >> something like that) >> >> >> >> Can we get these squashed Monday so we can verify the upgrades are >> >> otherwise green? >> >> >> >> Thanks! >> >> sage >> >> >> > >> > >> > >> > -- >> > Jason >> >> >> >> -- >> Jason >> -- >> 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 -- 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