<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 21, 2015 at 3:52 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">On Mon, Dec 21, 2015 at 2:10 PM, Yedidyah Bar David 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><div>On Sun, Dec 20, 2015 at 9:50 PM, Martin Perina wrote:<br>
><br>
><br></div></div></blockquote><div><br></div><div>[snip]</div><span class=""><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><div>
>><br>
>> So you should run engine-setup after you update this package.<br>
>><br>
>> Martin - is this intentional? Why not update the package automatically<br>
>> during engine-setup?<br>
>><br>
>> Or even version-lock it? I do not think people should expect their engine<br>
>> to not allow logins after they run 'yum update'. Adding also Sandro.<br>
><br>
> Hi,<br>
><br>
> there are several reasons for this:<br>
><br>
> 1. aaa-jdbc is an engine 3.6 extension, engine requires its presence to<br>
> provide 'internal' domain but it doesn't require any specific version,<br>
> so users may update aaa-jdbc independently on engine if they need<br>
> features provided provided by new version<br>
><br>
> 2. engine-setup automatically configures/upgrades 'internal' domain, but<br>
> users may define manually other domains (as described in README.admin)<br>
> and those domains are not touched by engine-setup at all<br>
><br>
> 3. Due to 1. and 2. we decided not to define version specific requirement<br>
> between engine and aaa-jdbc in engine-setup (same behaviour as already<br>
> exists for other engine extensions). So users may for example upgrade<br>
> engine, but leave aaa-jdbc as is or leave engine as is and upgrade<br>
> aaa-jdbc if they need it. Users just need to get used to read doc<br>
> before doing upgrade.<br>
<br>
</div></div>Now filed: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1293338" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1293338</a><br>
<br>
Best,<br>
<span><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></span></div><br></div><div class="gmail_extra"><div class="gmail_extra">Thanks, I gave my contribute inside the bugzilla.</div><div class="gmail_extra">I personally felt this behavior could potentially break many oVirt and possibly RHEV installations based on the internal profile and your action seems to confirm it.</div><div class="gmail_extra">As a user I disagree with Martin point in 3. as I'm usually inclined to read the docs but not all the READMEs provided by any single package in the system. I didn't find a clear reference to this step inside the oVirt web documentation, but I could be wrong. I rememebr about it only when I played with FreeIPA authentication in oVirt, but not in internal usage.</div><div class="gmail_extra">But if this problem can become an opportunity to make both docs and users better entities it's not a problem for me...</div><span class=""><font color="#888888"><div class="gmail_extra">Gianluca</div><div> </div></font></span></div></div>
</blockquote></div><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">In the mean time I was "able" to solve the problems following what already asked some days ago:</div><div class="gmail_extra"><a href="http://lists.ovirt.org/pipermail/users/2015-December/036601.html">http://lists.ovirt.org/pipermail/users/2015-December/036601.html</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">- verified no tasks on hypervisor as what found in business_entity_snapshot are failed attempts to import hosted engine storage domain</div><div class="gmail_extra"><div class="gmail_extra">[root@ractor ~]# vdsClient -s 0 getAllTasksStatuses</div><div class="gmail_extra">{'status': {'message': 'OK', 'code': 0}, 'allTasksStatus': {}}</div><div class="gmail_extra"><br></div><div class="gmail_extra">- stop engine</div><div class="gmail_extra">systemctl stop ovirt-engine</div><div class="gmail_extra"><br></div><div class="gmail_extra">- delete on db</div><div class="gmail_extra"><div class="gmail_extra">engine=# delete from business_entity_snapshot ;</div><div class="gmail_extra">DELETE 3</div><div class="gmail_extra">engine=# commit;</div><div class="gmail_extra">COMMIT</div><div class="gmail_extra">engine=# exit</div><div class="gmail_extra">engine-# \q</div><div class="gmail_extra">-bash-4.2$ exit</div><div class="gmail_extra">logout</div></div><div class="gmail_extra"><br></div><div class="gmail_extra">- start engine</div><div class="gmail_extra">systemctl start engine</div><div class="gmail_extra"><br></div><div class="gmail_extra">- update ovirt-engine-extension-aaa-jdbc</div><div class="gmail_extra"><div class="gmail_extra">---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.1-1.el7 will be updated</div><div class="gmail_extra">---> Package ovirt-engine-extension-aaa-jdbc.noarch 0:1.0.4-1.el7 will be an update</div><div class="gmail_extra"><br></div><div class="gmail_extra">- engine-setup now completes ok</div><div class="gmail_extra">(based on /usr/share/doc/ovirt-engine-extension-aaa-jdbc-1.0.4/README.admin as I have only internal profile)</div><div class="gmail_extra"><div class="gmail_extra">[root@ractorshe ovirt-engine]# engine-setup </div><div class="gmail_extra">[ INFO ] Stage: Initializing</div><div class="gmail_extra">[ INFO ] Stage: Environment setup</div><div class="gmail_extra"> 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 class="gmail_extra"> Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20151222171311-pad6e4.log</div><div class="gmail_extra"> Version: otopi-1.4.0 (otopi-1.4.0-1.el7.centos)</div><div class="gmail_extra">[ INFO ] Stage: Environment packages setup</div><div class="gmail_extra">[ INFO ] Stage: Programs detection</div><div class="gmail_extra">[ INFO ] Stage: Environment setup</div><div class="gmail_extra">[ INFO ] Stage: Environment customization</div><div class="gmail_extra"> </div><div class="gmail_extra"> --== PRODUCT OPTIONS ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== PACKAGES ==--</div><div class="gmail_extra"> </div><div class="gmail_extra">[ INFO ] Checking for product updates...</div><div class="gmail_extra">[ INFO ] No product updates found</div><div class="gmail_extra"> </div><div class="gmail_extra"> --== ALL IN ONE CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== NETWORK CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra">[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be resolved only locally</div><div class="gmail_extra"> Setup can automatically configure the firewall on this system.</div><div class="gmail_extra"> Note: automatic configuration of the firewall may overwrite current settings.</div><div class="gmail_extra"> Do you want Setup to configure the firewall? (Yes, No) [Yes]: Yes</div><div class="gmail_extra">[ INFO ] firewalld will be configured as firewall manager.</div><div class="gmail_extra">[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be resolved only locally</div><div class="gmail_extra">[WARNING] Failed to resolve ractorshe.my.domain using DNS, it can be resolved only locally</div><div class="gmail_extra"> </div><div class="gmail_extra"> --== DATABASE CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== OVIRT ENGINE CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== STORAGE CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== PKI CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== APACHE CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== SYSTEM CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== MISC CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> </div><div class="gmail_extra"> --== END OF CONFIGURATION ==--</div><div class="gmail_extra"> </div><div class="gmail_extra">[ INFO ] Stage: Setup validation</div><div class="gmail_extra"> During execution engine service will be stopped (OK, Cancel) [OK]: </div><div class="gmail_extra">[ INFO ] Cleaning stale zombie tasks and commands</div><div class="gmail_extra"> </div><div class="gmail_extra"> --== CONFIGURATION PREVIEW ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> Default SAN wipe after delete : False</div><div class="gmail_extra"> Firewall manager : firewalld</div><div class="gmail_extra"> Update Firewall : True</div><div class="gmail_extra"> Host FQDN : ractorshe.my.domain</div><div class="gmail_extra"> Engine database secured connection : False</div><div class="gmail_extra"> Engine database host : localhost</div><div class="gmail_extra"> Engine database user name : engine</div><div class="gmail_extra"> Engine database name : engine</div><div class="gmail_extra"> Engine database port : 5432</div><div class="gmail_extra"> Engine database host name validation : False</div><div class="gmail_extra"> Engine installation : True</div><div class="gmail_extra"> PKI organization : my.domain</div><div class="gmail_extra"> Configure VMConsole Proxy : True</div><div class="gmail_extra"> Engine Host FQDN : ractorshe.my.domain</div><div class="gmail_extra"> Configure WebSocket Proxy : True</div><div class="gmail_extra"> </div><div class="gmail_extra"> Please confirm installation settings (OK, Cancel) [OK]: </div><div class="gmail_extra">[ INFO ] Cleaning async tasks and compensations</div><div class="gmail_extra">[ INFO ] Unlocking existing entities</div><div class="gmail_extra">[ INFO ] Checking the Engine database consistency</div><div class="gmail_extra">[ INFO ] Stage: Transaction setup</div><div class="gmail_extra">[ INFO ] Stopping engine service</div><div class="gmail_extra">[ INFO ] Stopping ovirt-fence-kdump-listener service</div><div class="gmail_extra">[ INFO ] Stopping websocket-proxy service</div><div class="gmail_extra">[ INFO ] Stage: Misc configuration</div><div class="gmail_extra">[ INFO ] Stage: Package installation</div><div class="gmail_extra">[ INFO ] Stage: Misc configuration</div><div class="gmail_extra">[ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20151222171352.J1P6M4.dump'.</div><div class="gmail_extra">[ INFO ] Creating/refreshing Engine database schema</div><div class="gmail_extra">[ INFO ] Creating/refreshing Engine 'internal' domain database schema</div><div class="gmail_extra">[ INFO ] Upgrading CA</div><div class="gmail_extra">[ INFO ] Configuring WebSocket Proxy</div><div class="gmail_extra">[ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'</div><div class="gmail_extra">[ INFO ] Stage: Transaction commit</div><div class="gmail_extra">[ INFO ] Stage: Closing up</div><div class="gmail_extra"> </div><div class="gmail_extra"> --== SUMMARY ==--</div><div class="gmail_extra"> </div><div class="gmail_extra"> SSH fingerprint: 19:56:8d:3e:50:fc:90:37:5a:ba:6c:57:30:b1:7d:93</div><div class="gmail_extra"> Internal CA DA:E6:04:34:99:A0:DB:CE:3F:0A:7B:A2:96:67:4C:7F:19:CA:95:5F</div><div class="gmail_extra"> Note! If you want to gather statistical information you can install Reports and/or DWH:</div><div class="gmail_extra"> <a href="http://www.ovirt.org/Ovirt_DWH">http://www.ovirt.org/Ovirt_DWH</a></div><div class="gmail_extra"> <a href="http://www.ovirt.org/Ovirt_Reports">http://www.ovirt.org/Ovirt_Reports</a></div><div class="gmail_extra"> Web access is enabled at:</div><div class="gmail_extra"> <a href="http://ractorshe.my.domain:80/ovirt-engine">http://ractorshe.my.domain:80/ovirt-engine</a></div><div class="gmail_extra"> <a href="https://ractorshe.my.domain:443/ovirt-engine">https://ractorshe.my.domain:443/ovirt-engine</a></div><div class="gmail_extra"> </div><div class="gmail_extra"> --== END OF SUMMARY ==--</div><div class="gmail_extra"> </div><div class="gmail_extra">[ INFO ] Starting engine service</div><div class="gmail_extra">[ INFO ] Restarting httpd</div><div class="gmail_extra">[ INFO ] Restarting ovirt-vmconsole proxy service</div><div class="gmail_extra">[ INFO ] Stage: Clean up</div><div class="gmail_extra"> Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20151222171311-pad6e4.log</div><div class="gmail_extra">[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20151222171439-setup.conf'</div><div class="gmail_extra">[ INFO ] Stage: Pre-termination</div><div class="gmail_extra">[ INFO ] Stage: Termination</div><div class="gmail_extra">[ INFO ] Execution of setup completed successfully</div><div class="gmail_extra"><br></div><div class="gmail_extra">- Test with success login to webadmin portal with admin@internal and lates ovirt-engine-extension-aaa-jdbc applied</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca</div></div><div><br></div></div></div></div>