On 11/10/2022 06:59, Henrik K wrote:
On Tue, Oct 11, 2022 at 12:50:38AM +0200, Wolfgang Breyha wrote:
And another quite simple ruleset...
meta __SA4TA3_1 6
meta __SA4TA3_2 2
meta __SA4TA3 (__SA4TA3_1 > 2) && (__SA4TA3_2 > 1)
doesn't set __SA4TA3. This was working an SA3.4 as well.
Works fine here.
Really? So why doesn't it work here on RHEL7 and RHEL8?
Tried again with
meta __SA4TA3_1 6
meta __SA4TA3_2 2
meta SA4TA3 (__SA4TA3_1 > 2) && (__SA4TA3_2 > 1)
score SA4TA3 0.1
I see
dbg: rules: ran meta rule __SA4TA3_2 ======> got hit (2)
dbg: rules: ran meta rule __SA4TA3_1 ======> got hit (6)
But no line für SA4TA3 and no report or final score.
Is this wanted behavior or a bug? Since UPGRADE does not contain any
information about basic changes for meta rules I assume it is a
bug/regression. But if this is wanted how should this be done on SA4?
From UPGRADE:
- Meta rules no longer use priority values, they are evaluated
dynamically when the rules they depend on are finished. (Bug 7735)
I don't see the context with the above problem. Maybe that the dynamic
evaluation doesn't work in my case and the final rule is never evaluated.
But I still don't know how to possibly fix this on my side.
Greetings,
Wolfgang
