[Users] Regression/Bug in 3.2.3-1 Webadmin?

Hi, we get a notification each minute that "User admin@interal logged in". This bug was reported and fixed in https://bugzilla.redhat.com/show_bug.cgi?id=906046 for rhev. Can someone confirm to me that this fix got backported/ included in oVirt? We still face this issue, see the attached screenshot. Regards Sven

----- Original Message -----
From: "Sven Kieske" <S.Kieske@mittwald.de> To: users@ovirt.org Sent: Tuesday, October 8, 2013 11:16:51 AM Subject: [Users] Regression/Bug in 3.2.3-1 Webadmin?
Hi,
we get a notification each minute that "User admin@interal logged in".
This bug was reported and fixed in https://bugzilla.redhat.com/show_bug.cgi?id=906046 for rhev.
Can someone confirm to me that this fix got backported/ included in oVirt?
Patch that fixes this issue is http://gerrit.ovirt.org/#/c/14411/ (Change-Id I72c2d4952daac4daa17554b7661ed775c72cb97a) It's part of master branch, however it's NOT part of engine_3.2 branch. So this patch wasn't backported into engine_3.2 branch.
We still face this issue, see the attached screenshot.
Regards
Sven
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hi, so just to understand this: This patch got backported for the enterprise version rhev 3.2 but did not get backported for oVirt 3.2 ? I thought oVirt is the upstream project for rhev, is there some kind of policy which prevents these backports from being applied upstream, or what is the reason for this? Thanks for your fast reply and your great support! Regards Sven On 08.10.2013 14:12, Vojtech Szocs wrote:
----- Original Message -----
From: "Sven Kieske" <S.Kieske@mittwald.de> To: users@ovirt.org Sent: Tuesday, October 8, 2013 11:16:51 AM Subject: [Users] Regression/Bug in 3.2.3-1 Webadmin?
Hi,
we get a notification each minute that "User admin@interal logged in".
This bug was reported and fixed in https://bugzilla.redhat.com/show_bug.cgi?id=906046 for rhev.
Can someone confirm to me that this fix got backported/ included in oVirt?
Patch that fixes this issue is http://gerrit.ovirt.org/#/c/14411/ (Change-Id I72c2d4952daac4daa17554b7661ed775c72cb97a)
It's part of master branch, however it's NOT part of engine_3.2 branch. So this patch wasn't backported into engine_3.2 branch.
We still face this issue, see the attached screenshot.
Regards
Sven
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 10/08/2013 03:54 PM, Sven Kieske wrote:
Hi,
so just to understand this:
This patch got backported for the enterprise version rhev 3.2 but did not get backported for oVirt 3.2 ?
I thought oVirt is the upstream project for rhev, is there some kind of policy which prevents these backports from being applied upstream, or what is the reason for this?
there isn't such a policy. they just happened to have different cut-off times previously, and we're actually doing much more efforts on 3.3 stable branch of ovirt to align cut-off better. it's in 3.3. if 3.3 isn't viable, then if you want it backported to ovirt 3.2, shouldn't be an issue to backport, but please raise it in the wednesday meeting to ask for a 3.2.z to be spinned with it. thanks, Itamra
Thanks for your fast reply and your great support!
Regards
Sven
On 08.10.2013 14:12, Vojtech Szocs wrote:
----- Original Message -----
From: "Sven Kieske" <S.Kieske@mittwald.de> To: users@ovirt.org Sent: Tuesday, October 8, 2013 11:16:51 AM Subject: [Users] Regression/Bug in 3.2.3-1 Webadmin?
Hi,
we get a notification each minute that "User admin@interal logged in".
This bug was reported and fixed in https://bugzilla.redhat.com/show_bug.cgi?id=906046 for rhev.
Can someone confirm to me that this fix got backported/ included in oVirt?
Patch that fixes this issue is http://gerrit.ovirt.org/#/c/14411/ (Change-Id I72c2d4952daac4daa17554b7661ed775c72cb97a)
It's part of master branch, however it's NOT part of engine_3.2 branch. So this patch wasn't backported into engine_3.2 branch.
We still face this issue, see the attached screenshot.
Regards
Sven
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Hi, no problem, we are evaluating 3.3 as well, so we may not need this in 3.2 if our testing with 3.3 succeeds. Thanks for your clarification anyway! PS: The meetings all take place on #ovirt irc? what is the time schedule? Regards Sven On 08.10.2013 15:08, Itamar Heim wrote:
On 10/08/2013 03:54 PM, Sven Kieske wrote:
Hi,
so just to understand this:
This patch got backported for the enterprise version rhev 3.2 but did not get backported for oVirt 3.2 ?
I thought oVirt is the upstream project for rhev, is there some kind of policy which prevents these backports from being applied upstream, or what is the reason for this?
there isn't such a policy. they just happened to have different cut-off times previously, and we're actually doing much more efforts on 3.3 stable branch of ovirt to align cut-off better.
it's in 3.3. if 3.3 isn't viable, then if you want it backported to ovirt 3.2, shouldn't be an issue to backport, but please raise it in the wednesday meeting to ask for a 3.2.z to be spinned with it.
thanks, Itamra

On 10/08/2013 04:22 PM, Sven Kieske wrote:
Hi,
no problem, we are evaluating 3.3 as well, so we may not need this in 3.2 if our testing with 3.3 succeeds.
Thanks for your clarification anyway!
PS: The meetings all take place on #ovirt irc? what is the time schedule?
yes, on #ovirt irc. wednesday, 10am EST for the general weekly meeting .
Regards
Sven
On 08.10.2013 15:08, Itamar Heim wrote:
On 10/08/2013 03:54 PM, Sven Kieske wrote:
Hi,
so just to understand this:
This patch got backported for the enterprise version rhev 3.2 but did not get backported for oVirt 3.2 ?
I thought oVirt is the upstream project for rhev, is there some kind of policy which prevents these backports from being applied upstream, or what is the reason for this?
there isn't such a policy. they just happened to have different cut-off times previously, and we're actually doing much more efforts on 3.3 stable branch of ovirt to align cut-off better.
it's in 3.3. if 3.3 isn't viable, then if you want it backported to ovirt 3.2, shouldn't be an issue to backport, but please raise it in the wednesday meeting to ask for a 3.2.z to be spinned with it.
thanks, Itamra
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Itamar Heim
-
Sven Kieske
-
Vojtech Szocs