<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 14, 2015 at 4:39 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Mon, Dec 14, 2015 at 4:10 PM, Sandro Bonazzola 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><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><br><div><br></div></span><div>You should just activate it.</div><div>Adding Roy, looks like this doesn't happen to me only.</div><div><br></div></div></div></div></blockquote><div><br></div></span><div>See <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1290518" style="color:rgb(102,153,204);text-decoration:none;font-family:'DejaVu Sans','Liberation Sans',sans-serif;font-size:16.25px;font-weight:bold" target="_blank"><b>Bug 1290518</b></a><span style="color:rgb(0,0,0);font-family:'DejaVu Sans','Liberation Sans',sans-serif;font-size:16.25px;font-weight:bold;background-color:rgb(208,208,208)"> -</span><span style="color:rgb(0,0,0);font-family:'DejaVu Sans','Liberation Sans',sans-serif;font-size:16.25px;font-weight:bold"> <span>failed Activating hosted engine domain during auto-import on NFS</span></span></div><span><div><br></div></span></div></div></div></blockquote><div><br></div></span><div>I confirm that I hit the bug and I was able to simply activate the storage domain and able to see the engine vm</div><div><br></div><div><div>Dec 14, 2015 4:22:23 PM Hosted Engine VM was imported successfully</div><div>Dec 14, 2015 4:22:23 PM Starting to import Vm HostedEngine to Data Center Default, Cluster Default<span style="white-space:pre-wrap"> </span></div><div>Dec 14, 2015 4:22:19 PM Storage Domain hosted_storage (Data Center Default) was activated by admin@internal</div></div><div><br></div><div><br></div><div>NOTES:</div><div>1) I configured the engine vm as a vnc one during install (in 3.6.0, as the appliance was the 3.6.0 one as we noted)</div><div><br></div><div><div>[ INFO ] Stage: Setup validation</div><div><br></div><div> --== CONFIGURATION PREVIEW ==--</div><div> </div><div> Bridge interface : eth0</div><div> Engine FQDN : shengine.localdomain.local</div><div> Bridge name : ovirtmgmt</div><div> SSH daemon port : 22</div><div> Firewall manager : iptables</div><div> Gateway address : 192.168.122.1</div><div> Host name for web application : hosted_engine_1</div><div> Host ID : 1</div><div> Image size GB : 10</div><div> GlusterFS Share Name : hosted_engine_glusterfs</div><div> GlusterFS Brick Provisioning : False</div><div> Storage connection : ovc71.localdomain.local:/SHE_DOMAIN</div><div> Console type : vnc</div><div> Memory size MB : 8192</div><div> MAC address : 00:16:3e:72:e7:26</div><div> Boot type : disk</div><div> Number of CPUs : 1</div><div> OVF archive (for disk boot) : /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-3.6-20151211.1.el7.centos.ova</div><div> Restart engine VM after engine-setup: True</div><div> CPU Type : model_Nehalem </div><div><br></div><div> Please confirm installation settings (Yes, No)[Yes]: </div></div><div><br></div><div>but after import in 3.6.1 I see it configured as with spice console in web admin gui.</div><div>I indeed am able to access it via spice, but just to notice that if one eventually would like to have it vnc, he/she has to edit the engine vm after update to 3.6.1.....</div><div>BTW: is it possible/supported to edit engine vm from the gui and change for example the console mode?</div><div><br></div><div>2) During setup, see above, it was configured with iptables as firewall manager</div><div>During the update to 3.6.1 this was the workflow shown at video:</div><div> <br></div><div><div>[root@shengine ~]# engine-setup</div><div>[ INFO ] Stage: Initializing</div><div>[ INFO ] Stage: Environment setup</div><div> Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']</div><div> Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20151214134331-ga1lxy.log</div><div> Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos)</div><div>[ INFO ] Stage: Environment packages setup</div><div>[ INFO ] Stage: Programs detection</div><div>[ INFO ] Stage: Environment setup</div><div>[ INFO ] Stage: Environment customization</div><div> </div><div> --== PRODUCT OPTIONS ==--</div><div> </div><div> </div><div> --== PACKAGES ==--</div><div> </div><div>[ INFO ] Checking for product updates...</div><div> Setup has found updates for some packages:</div><div> PACKAGE: [updated] ovirt-engine-3.6.0.3-1.el7.centos.noarch</div></div><div>...</div><div><div> PACKAGE: [update] ovirt-engine-wildfly-overlay-8.0.4-1.el7.noarch</div><div> do you wish to update them now? (Yes, No) [Yes]: </div></div><div><div> [ INFO ] Checking for an update for Setup...</div><div> </div><div> --== ALL IN ONE CONFIGURATION ==-- </div><div><br></div><div> --== NETWORK CONFIGURATION ==--</div><div> </div><div> Setup can automatically configure the firewall on this system.</div><div> Note: automatic configuration of the firewall may overwrite current settings.</div><div> Do you want Setup to configure the firewall? (Yes, No) [Yes]: </div><div>[ INFO ] firewalld will be configured as firewall manager.</div></div><div><br></div><div>So the former setup was with iptables durinh sh engine setup in 3.6.0 while then with firewalld in 3.6.1.</div><div><br></div><div>In fact on the engine I see</div><div><br></div><div><br></div><div><div>[root@shengine ~]# systemctl status iptables</div><div>iptables.service</div><div> Loaded: not-found (Reason: No such file or directory)</div><div> Active: inactive (dead)</div><div><br></div><div>[root@shengine ~]# systemctl status firewalld</div><div>firewalld.service - firewalld - dynamic firewall daemon</div><div> Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)</div><div> Active: active (running) since Mon 2015-12-14 14:19:56 UTC; 1h 15min ago</div><div> Main PID: 431 (firewalld)</div><div> CGroup: /system.slice/firewalld.service</div><div> └─431 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid</div><div><br></div><div>Dec 14 14:19:53 shengine.localdomain.local systemd[1]: Starting firewalld - dynamic firewall da.....</div><div>Dec 14 14:19:56 shengine.localdomain.local systemd[1]: Started firewalld - dynamic firewall daemon.</div><div>Hint: Some lines were ellipsized, use -l to show in full.</div></div><div><br></div><div><br></div><div>Or is it the firewall manager asked during the initial hosted engine setup related to the host itself and not the engine vm perhaps???</div></div></div></div></blockquote><div><br></div><div>Exactly.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="HOEnZb"><font color="#888888"><div><br></div><div>Gianluca</div></font></span></div></div></div>
</blockquote></div><br></div></div>