<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Dec 19, 2015 at 8:16 PM, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>></span> wrote:<br><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"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Sat, Dec 19, 2015 at 7:58 PM, Oved Ourfali <span dir="ltr"><<a href="mailto:oourfali@redhat.com" target="_blank">oourfali@redhat.com</a>></span> wrote:<br><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"><p dir="ltr">Reading it again, I'm not sure the engine was even tested with centos 7. <br>
As far as I know only centos 6 is supported/tested for the engine machine.</p></blockquote></span><div><div>Our ovirt-engine-appliance is already based on Centos 7 so I think that a consistent part of our 3.6 upstream user is already on that.</div><div><br></div><div>[root@enginevm ~]# cat /etc/redhat-release </div><div>CentOS Linux release 7.2.1511 (Core) </div></div><div><div class="h5"><div><br></div><div> </div></div></div></div></div></div></blockquote><div><br></div><div>Yes, for engine VM in HE I used the oVirt shipped appliance that was already in CentOS 7.1 and the flow I was trying to complete was to update it to 7.2 as supported.</div><div><br></div><div>From the last output I sent it seems in some way sanlock was responsible for the detath of engineVM right after completion of engine-setup.</div><div>And possibly causing any corruption inside the db</div><div>If it can be of any help, here the contents of the two tables involved</div><div><br></div><div>storage_domain_static<br></div><div>and</div><div>storage_domain_dynamic<br></div><div><br></div><div><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvU0RoZjFZSzRKbzQ/view?usp=sharing">https://drive.google.com/file/d/0BwoPbcrMv8mvU0RoZjFZSzRKbzQ/view?usp=sharing</a><br></div><div><br></div><div>If you have any othr quey to run against db....</div><div><br></div><div>but I don't understand how this can influence the fact that inside the web ui login I don't see any selectable value for the profile field: the "internal" default domain is missing.... I didn't implement any other </div><div><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sharing">https://drive.google.com/file/d/0BwoPbcrMv8mvNTV1S2M3MGdKNHM/view?usp=sharing</a><br></div><div><br></div><div>Gianluca <br></div></div></div></div>