<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Oct 23, 2014 at 9:51 PM, Roy Golan <span dir="ltr"><<a href="mailto:rgolan@redhat.com" target="_blank">rgolan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1145241" target="_blank">https://bugzilla.redhat.com/<u></u>show_bug.cgi?id=1145241</a><br>
</blockquote></span>
patch sent [3] - it will create a default disk profile for each data domain. If any of you could verify it that will be great.<br>
[3] <a href="http://gerrit.ovirt.org/#/c/34422/" target="_blank">http://gerrit.ovirt.org/#/c/<u></u>34422/</a><div class="HOEnZb"><div class="h5"><br></div></div></blockquote></div><br></div><div class="gmail_extra">Hi, what is the workflow for testing?<br></div><div class="gmail_extra">I'm going to update an All-In-One environment from 3.4.4 to 3.5.0 (I just asked some related questions in a separate thread) so that I can test it.<br></div><div class="gmail_extra">Do I have to apply the patch right after the yum update step and before the engine-setup one?<br><br></div><div class="gmail_extra">What to do for existing environments for testing? Patch and verify correct setup for new storage domains or anything also for pre-existing ones?<br><br></div><div class="gmail_extra">Gianluca<br></div><div class="gmail_extra"><br></div></div>