<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 22, 2013 at 6:13 AM, Gary Kotton <span dir="ltr"><<a href="mailto:gkotton@vmware.com" target="_blank">gkotton@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Dolph please see - <a href="https://github.com/openstack/tempest/blob/stable/grizzly/tools/pip-requires#L10" target="_blank">https://github.com/openstack/tempest/blob/stable/grizzly/tools/pip-requires#L10</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">This could be the cause of the problem. I think that either we need to lock down the client for the stable/grizzly tempest branch or add netaddr. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">What do you guys suggest?</span></p></div></div></blockquote><div><br></div><div>The latest clients should be continuously tested against the stable branches, so I'd rather not lock the client down if it can be avoided. Is there any reason *not* to allow netaddr as a client side dep?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">At the moment the reviews are piling up…<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Gary<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Dolph Mathews [mailto:<a href="mailto:dolph.mathews@gmail.com" target="_blank">dolph.mathews@gmail.com</a>] <br>
<b>Sent:</b> Wednesday, August 21, 2013 4:07 PM<br><b>To:</b> Alan Pevec<br><b>Cc:</b> Gary Kotton; <a href="mailto:openstack-stable-maint@lists.openstack.org" target="_blank">openstack-stable-maint@lists.openstack.org</a></span></p>
<div><br><b>Subject:</b> Re: [Openstack-stable-maint] Stable grizzly failures<u></u><u></u></div><p></p></div></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal"><u></u> <u></u></p><div><div>
<p class="MsoNormal">On Wed, Aug 21, 2013 at 4:00 AM, Alan Pevec <<a href="mailto:apevec@gmail.com" target="_blank">apevec@gmail.com</a>> wrote:<u></u><u></u></p><div><div><p class="MsoNormal">Hi Gary,<br>
<br>we should figure out which version of keystoneclient Tempest is using,<br>I could not parse that information from tempest log.<br>At the same time, keystone jobs are failing with ImportError: No<br>module named netaddr in common/jsonutils, that's a design issue with<br>
test_keystoneclient in Keystone: checking out keystoneclient from git<br>master, assuming dependecies didn't change since last release, which<br>isn't the case since[1] was merged after 0.3.1.<br>Quick fix would be to release a new keystoneclient which has updated<br>
requirements, so new deps get pulled into venv.<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">If that happens to be acceptable fix, I was intending to release a new version of keystoneclient in the next day or so anyway.<u></u><u></u></p>
</div><div><p class="MsoNormal"> <u></u><u></u></p></div><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"><p class="MsoNormal"><br>Besides those keystoneclient related failures, we have Glance and Heat<br>
jobs failing and returning back to normal randomly.<br><br>Cheers,<br>Alan<br><br>[1] <a href="https://github.com/openstack/python-keystoneclient/commit/de72de3b809c53420d2936b619d613c4294e4329" target="_blank">https://github.com/openstack/python-keystoneclient/commit/de72de3b809c53420d2936b619d613c4294e4329</a><br>
<br>_______________________________________________<br>Openstack-stable-maint mailing list<br><a href="mailto:Openstack-stable-maint@lists.openstack.org" target="_blank">Openstack-stable-maint@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint</a><u></u><u></u></p>
</blockquote></div></div></div><p class="MsoNormal"><br><br clear="all"><u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">-- <u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p>
</div><p class="MsoNormal">-Dolph <u></u><u></u></p></div></div></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><br></div>-Dolph
</div></div>