<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt><br>
    </tt>
    <div class="moz-cite-prefix"><tt>On 04/07/2015 09:28 PM, John
        Griffith wrote:</tt><tt><br>
      </tt></div>
    <blockquote
cite="mid:CA+qL3LXJY6s7Vag0nhjzV2APHVpS1jPjGKcsteu6QkGsSFOS7A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_default"><tt><br>
          </tt></div>
        <div class="gmail_extra"><tt><br>
          </tt>
          <div class="gmail_quote"><tt>On Tue, Apr 7, 2015 at 6:27 AM,
              Deepak C Shetty </tt><tt><span dir="ltr">&lt;<a
                  moz-do-not-send="true"
                  href="mailto:deepakcs@redhat.com" target="_blank">deepakcs@redhat.com</a>&gt;</span></tt><tt>
              wrote:</tt><tt><br>
            </tt>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><tt>Hi
                CI'ers :)</tt><tt><br>
              </tt><tt>
                    Just wanted to send a quick update on the glusterfs
                CI job (check-tempest-dsvm-full-</tt><tt>glusterfs-nv)
                currently failing on most patches, is due to the
                recently enabled test_volume_boot_pattern which is
                failing for glusterfs backend.</tt><tt><br>
              </tt>
              <tt><br>
              </tt><tt>
                   I have opened LP bug </tt><tt><a
                  moz-do-not-send="true"
                  href="https://bugs.launchpad.net/cinder/+bug/1441050"
                  target="_blank">https://bugs.launchpad.net/cinder/+bug/1441050</a></tt><tt>
                to track the issue.</tt><tt><br>
              </tt><tt>
                Bharat (in CC) is actively working on it.</tt><tt><br>
              </tt>
              <tt><br>
              </tt><tt>
                  I would like to know if we continue with the
                status-quo or disable this testcase for glusterfs until
                this bug is fixed ?</tt><tt><br>
              </tt>
              <tt><br>
              </tt><tt>
                thanx,</tt><tt><br>
              </tt><tt>
                deepak</tt><tt><br>
              </tt>
              <tt><br>
              </tt>
              <tt><br>
              </tt><tt>
                ______________________________</tt><tt>_________________</tt><tt><br>
              </tt><tt>
                Third-party-announce mailing list</tt><tt><br>
              </tt>
              <tt><a moz-do-not-send="true"
                  href="mailto:Third-party-announce@lists.openstack.org"
                  target="_blank">Third-party-announce@lists.openstack.org</a></tt><tt><br>
              </tt>
              <tt><a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce"
                  target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce</a></tt><tt><br>
              </tt>
            </blockquote>
          </div>
          <div class="gmail_default"><tt>Seems the trend for Ceph is to
              add a skip [1].  Personally I'd like to see some more
              analysis before just skipping, even better actually see
              the problem fixed.  For the record, I'm not a fan of
              immediately skipping/disabling for a single backend. 
              We've been pretty hard on Vendors the last few weeks that
              weren't running all of the same tests as the reference
              implementation.  But in the case of Ceph and now Gluster
              it seems we have "different" standards.</tt></div>
          <div class="gmail_default"><tt><br>
            </tt></div>
          <div class="gmail_default"><tt>Don't get me wrong, I'm not
              opposed to this, and I gave my +1 to the Ceph patch (and
              would give it to the Gluster patch with more info).  I'm
              just saying however that we need to get some consistency
              here and treat everybody fairly.  I spent "A LOT" of time
              this release cycle making sure my device and the LVM
              device worked properly, significantly more on LVM.  </tt></div>
          <div class="gmail_default"><tt><br>
            </tt></div>
          <div class="gmail_default"><tt>I proposed a temporary skip for
              LVM once and it was adamantly rejected.  I then proposed a
              sleep in Nova for the LVM driver, again rejected.  The
              response has been "The issue needs to be fixed or at least
              completely understood".  Same holds true here in my
              opinion.</tt></div>
        </div>
      </div>
    </blockquote>
    <tt><br>
    </tt><tt>Thanks John for your verbose opinion :) I am with you on
      this.</tt><tt><br>
      <br>
    </tt><tt>My only intent of skipping was to make sure the CI job
      doesn't add un-necessary noise on the patches and/or community
      thinking wrongly about the CI job, just because 1 of the 300+ tests
      are failing. We are actively working on the fix and we have
      figured the problem (see the LP bug) &amp; working on the solution</tt><tt><br>
    </tt><tt><br>
    </tt><tt>thanx,</tt><tt><br>
    </tt><tt>deepak</tt><tt><br>
    </tt><tt><br>
    </tt>
    <blockquote
cite="mid:CA+qL3LXJY6s7Vag0nhjzV2APHVpS1jPjGKcsteu6QkGsSFOS7A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_default"><tt><br>
            </tt></div>
          <div class="gmail_default"><tt>Thanks,</tt></div>
          <div class="gmail_default"><tt>John</tt></div>
          <div class="gmail_default"><tt><br>
            </tt></div>
          <div class="gmail_default"><tt>[1]: </tt><tt><a
                moz-do-not-send="true"
                href="https://review.openstack.org/#/c/170903/">https://review.openstack.org/#/c/170903/</a></tt></div>
          <tt><br>
          </tt></div>
      </div>
    </blockquote>
    <tt><br>
    </tt>
  </body>
</html>