Even when Augeas support is disabled for an Apache Web Server resource, the Apache plug-in continues to use Augeas in some circumstances.
The loadResourceConfiguration() method of the following classes seems to be the offender:
The expectation is that if Augeas Support is disabled in the plug-in configuration, no method will attempt to use it.
(8:07:49 AM) lkrejci: ccrouch-afk: ah, no, it isn't - i lied to you the last time ;) the components mentioned in the description just lack the check for augeas being allowed by the user and just use it..
(8:08:04 AM) ccrouch: sigh
(8:08:18 AM) ccrouch: ok, thats going to need fixing too then
(8:08:41 AM) lkrejci: but this is only a issue if you do: 1) inventory apache, 2) enable augeas, 3) change your mind and disable it after a while
(8:08:58 AM) ccrouch: good point
(8:09:11 AM) lkrejci: k, i'll take a look at it now
(8:09:18 AM) lkrejci: shouldn't be a problem
(8:09:30 AM) ccrouch: ok so we should fix it, but its not a blocker i guess
(8:09:55 AM) lkrejci: yea, i don't think it's a blocker
remove superfluous blocks bz's
BZ 717787 - Making sure augeas is only ever used if the apache resource
is allowed to do so.
Improved the confusing error message when augeas was not enabled that
stated that apache version is not supported or augeas is not available,
when in fact neither could be true.
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE