<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 class=""><div class="h5">On Sun, Dec 20, 2015 at 9:50 PM, Martin Perina wrote:<br>
><br>
><br></div></div></blockquote><div><br></div><div>[snip]</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 class=""><div class="h5">
>><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 class=""><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></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><div class="gmail_extra">Gianluca</div><div> </div></div></div>