Bug #3870
closedTechnique "Sudo utility configuration": Technique is not correctly reporting when applied by multiple rules
Description
Here is the correct result when one sudo directive is applied:
2013-08-22 18:17 result_success default_sudo_settings Default: sudo settings sudoersFile - The sudoers file did not require any modification 2013-08-22 18:17 result_success default_sudo_settings Default: sudo settings Install - sudo already installed 2013-08-22 18:16 result_success default_sudo_settings Default: sudo settings Permissions it_xx The group it_xx is already present 2013-08-22 18:16 result_success default_sudo_settings Default: sudo settings Permissions it_xxx The group it_xxx is already present
And here is the result when a second one is added in another rule:
2013-08-23 10:31 result_success default_sudo_settings Default: sudo settings sudoersFile - The sudoers file did not require any modification 2013-08-23 10:31 result_success oracle_sudo_settings Default: Oracle basic Install - sudo already installed 2013-08-23 10:31 result_success default_sudo_settings Default: sudo settings Install - sudo already installed 2013-08-23 10:31 result_success oracle_sudo_settings Default: Oracle basic Permissions it_zz The group it_zz is already present 2013-08-23 10:31 result_success default_sudo_settings Default: sudo settings Permissions it_xxx The group it_xxx is already present 2013-08-23 10:31 result_success default_sudo_settings Default: sudo settings Permissions it_xx The group it_xx is already present
Another example with another second rule:
2013-08-23 10:39 result_success default_sudo_settings Default: sudo settings sudoersFile - The sudoers file did not require any modification 2013-08-23 10:39 result_success perforce_sudo_settings Tuning: Perforce Install - sudo already installed 2013-08-23 10:39 result_success default_sudo_settings Default: sudo settings Install - sudo already installed 2013-08-23 10:39 result_success perforce_sudo_settings Tuning: Perforce Permissions perforce The user perforce is already present 2013-08-23 10:39 result_success perforce_sudo_settings Tuning: Perforce Permissions p4_admins The group p4_admins is already present 2013-08-23 10:39 result_success default_sudo_settings Default: sudo settings Permissions it_xx The group it_xx is already present 2013-08-23 10:39 result_success perforce_sudo_settings Tuning: Perforce Permissions perforce The user perforce is already present 2013-08-23 10:39 result_success perforce_sudo_settings Tuning: Perforce Permissions perforce The user perforce is already present 2013-08-23 10:39 result_success perforce_sudo_settings Tuning: Perforce Permissions perforce The user perforce is already present 2013-08-23 10:39 result_success default_sudo_settings Default: sudo settings Permissions it_xxx The group it_xxx is already present
I tried changing directive priorities, oracle_sudo_settings has now priority 10 but it hasn't changed anything.
The resulting issue, is that for rudder, the compliance isn't achieved and the reporting show an unknown state.
Updated by Nicolas PERRON about 11 years ago
- Status changed from New to In progress
- Assignee set to Nicolas PERRON
Thank for your report, I will look into this. Are these output from the Technical logs ?
Updated by Nicolas PERRON about 11 years ago
I've try to reproduce but my report is not in a 'Unknown' state. Nevertheless, one of the Rule is in 'No answer' which is normal due to the report missing for "sudoersFile".
Updated by Olivier Mauras about 11 years ago
My bad, it's rule that is in "unknown" state, report is indeed in "No answer"
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.7.1 to 2.4.8
This bug exists since the begining of time then the correct branch is 2.4.
I'm on it.
Updated by Nicolas PERRON about 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas PERRON to Matthieu CERDA
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/176
Pull Request URL added: https://github.com/Normation/rudder-techniques/pull/176
Matthieu, could you review it please ?
Updated by Nicolas PERRON about 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset policy-templates:commit:48debb51deb9d9049cf4e73cc08f998ccad63769.
Updated by Jonathan CLARKE about 11 years ago
Applied in changeset policy-templates:commit:b5ff338974c7595d7206da23fa4c6e41475e6cc2.
Updated by Nicolas PERRON about 11 years ago
- Subject changed from Sudo techniques not reporting correctly when applied by multiple rules to Technique "Sudo utility configuration": Technique is not correctly reporting when applied by multiple rules
Updated by Nicolas PERRON about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.8, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-September/000044.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog24
- Download information: http://www.rudder-project.org/foswiki/Download/