1 Reply Latest reply on Dec 5, 2012 2:58 PM by Eugene Brown

    Local Extended Object in compliance fail

      in a component template I created a local extended object


      "/usr/bin/zypper pchk | /usr/bin/grep needed"


      to run local


      in the compliance rule I use


      "Extended Object Entry:Patch Count".Name = 0


      the output of the command would look like this


      484 patches needed (173 security patches)


      When I run the compliance it always fails, but looking at the result all it ever shows is

      left hand side                  operator  

      extended object entry     exists


      I want to compare the outpur and see the compliance fails the 484 value.


      What am I doing wrong for a local extended object?


      The same command as an extended object works just fine.