<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 22, 2015 at 4:28 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.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"><div class="gmail_extra"><div class="gmail_quote"><span>On Thu, Oct 22, 2015 at 3:01 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"><div class="gmail_extra"><div class="gmail_quote"><div><div><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"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div><br></div><div>Any particular file or section in log files to cross check?</div><div>I can also start from scratch in case.... just to be sure that I don't get into same problem, so that it can be useful to find it before...</div><div><br></div></div></div></div></blockquote><div><br></div></div></div><div>I suspect that that host-deploy fails cause you have in place a leftover VDSM cert from the previous attempt which is still signed by your previous attempt engine and so it fails to match this new engine: on the second attempt hosted-engine-setup deployed again the engine appliance creating a new instance with different certs.</div><div><br></div></div></div></div></blockquote><div><br></div></span><div>I decided to restart clean and in fact all went well.</div><div>Last lines of output of "hosted-engine --deploy"</div><div><br></div><div>...</div><div><span><div>[ INFO ] Connecting to the Engine</div><div>[ INFO ] Waiting for the host to become operational in the engine. This may take several minutes...</div><div>[ INFO ] Still waiting for VDSM host to become operational...</div></span><div>[ INFO ] The VDSM Host is now operational</div><span><div>[ INFO ] Saving hosted-engine configuration on the shared storage domain</div><div>[ INFO ] Shutting down the engine VM</div><div>[ INFO ] Enabling and starting HA services</div><div> Hosted Engine successfully set up</div><div>[ INFO ] Stage: Clean up</div></span><div>[ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20151022160359.conf'</div><span><div>[ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'</div><div>[ INFO ] Stage: Pre-termination</div><div>[ INFO ] Stage: Termination</div></span></div><div><br></div><div>engine is up and admin web portal accessible and host results up.</div><div><br></div><div>I expected storage to be configured inside admin web portal but apparently I don't see anything already configured and also I don't see the sh engine VM listed... is it correct?</div></div></div></div></blockquote><div><br></div><div>No, we have an open bug on that:</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1269768" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1269768</a><br></div><div><br></div><div>You can try to manually import it in the mean time.</div><div><br></div><div>But hosted-engine storage domain can just contain the engine VM so you still need to add a regular storage domain for other VMs.</div><div><br></div><div> </div><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"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Filesystem layout at this time on the hypervisor is this:</div><div><div>[root@ovc71 tmp]# df -h</div><div>Filesystem Size Used Avail Use% Mounted on</div><div>/dev/mapper/centos-root 27G 2.7G 24G 11% /</div><div>devtmpfs 3.9G 0 3.9G 0% /dev</div><div>tmpfs 3.9G 4.0K 3.9G 1% /dev/shm</div><div>tmpfs 3.9G 8.7M 3.9G 1% /run</div><div>tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup</div><div>/dev/sda1 497M 130M 368M 27% /boot</div><div>/dev/mapper/OVIRT_DOMAIN-ISO_DOMAIN 5.0G 33M 5.0G 1% /ISO_DOMAIN</div><div>/dev/mapper/OVIRT_DOMAIN-NFS_DOMAIN 45G 2.7G 43G 6% /NFS_DOMAIN</div><div>ovc71.localdomain.local:/NFS_DOMAIN 45G 2.7G 43G 6% /rhev/data-center/mnt/ovc71.localdomain.local:_NFS__DOMAIN</div><div>/dev/loop1 2.0G 3.1M 1.9G 1% /rhev/data-center/mnt/_var_lib_ovirt-hosted-engine-setup_tmpUEso__Q</div></div><div><br></div><div>BTW: what is the 2Gb file system on loop device?</div></div></div></div></blockquote><div><br></div><div>It was used by hosted-engine-setup as a fake storage pool to bootstrap the hosted-engine storage domain.</div><div>It shouldn't be there at the end.</div><div>Could you please attach hosted-engine-setup logs to let me check why it's still there?</div><div> </div><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"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>I configured the storage domain part as NFS, pointing to ovc71.localdomain.local:/NFS_DOMAIN</div><div>Reading page at</div><div><a href="http://www.ovirt.org/Features/Self_Hosted_Engine" target="_blank">http://www.ovirt.org/Features/Self_Hosted_Engine</a><br></div><div><br></div><div>it is not clear to me what to do next if I want for example keep a single host with its sh engine as a replacement concept of what before was all-in-one... and start creating VMs....</div></div></div></div></blockquote><div><br></div><div>You have to setup your first regular data domain for other VMs: you can add another NFS one.</div><div> </div><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"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Output of my web admin page:</div><div><a href="https://drive.google.com/file/d/0BwoPbcrMv8mva3UyMTFDbHdsN3c/view?usp=sharing" target="_blank">https://drive.google.com/file/d/0BwoPbcrMv8mva3UyMTFDbHdsN3c/view?usp=sharing</a><br></div><div><br></div><div>Also, I didn't restart my hypervisor yet.</div><div>WHat should be the shutdown procedure? SImply run shutdown on hypervisor or</div><div>1) shutdwn engine vm</div><div>2) shutdown hypervisor</div><div>?</div><span><font color="#888888"><div><br></div></font></span></div></div></div></blockquote><div><br></div><div>Put the host in global maintenance (otherwise the engine VM will be restarted)</div><div>Shutdown the engine VM</div><div>Shutdown the host</div><div> </div><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"><div class="gmail_extra"><div class="gmail_quote"><span><font color="#888888"><div></div><div><br></div><div>Gianluca</div><div><br></div></font></span></div></div></div>
</blockquote></div><br></div></div>