Bug #13330
closed
NO_PASSWD: ALL not being added to sudoers file
Description
Despite issue #12782, I'm not seeing the NO_PASSWD being added. I was on version 4.3.2 and discovered the problem. Upgraded to 4.3.4 when I came across issue 12782. No change. Deleted rule, recreated rule. Removed the relevant %begin_section to %end_section from sudoers and sudoers.rudder each time... I do see the changes introduced by #12782 in sudoParameters/3.2/sudoParameters.st on the server.
Server:
[root@scrm-rudder ec2-user]# rpm -qa |grep rudder
rudder-inventory-endpoint-4.3.4.release-1.EL.7.noarch
rudder-server-root-4.3.4.release-1.EL.7.noarch
rudder-techniques-4.3.4.release-1.EL.7.noarch
rudder-agent-4.3.4.release-1.EL.7.x86_64
rudder-jetty-4.3.4.release-1.EL.7.noarch
rudder-webapp-4.3.4.release-1.EL.7.noarch
rudder-inventory-ldap-4.3.4.release-1.EL.7.x86_64
rudder-reports-4.3.4.release-1.EL.7.noarch
rudder-server-relay-4.3.4.release-1.EL.7.x86_64
Client:
[root@confluence rudder]# rpm -qa |grep rudder
rudder-agent-4.3.4.release-1.EL.7.x86_64
[root@confluence rudder]# cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
Updated by Nicolas CHARLES about 6 years ago
Hi Mike,
When you upgrade Rudder, techniques are not automatically upgraded, it needs a manual step (see https://www.rudder-project.org/doc-4.3/_technique_upgrade.html )
Did you upgrade your Techniques ?
If so, we'll need to know what values you set in the Directive, to reproduce the issue
If not, can you please first follow the procedure in https://www.rudder-project.org/doc-4.3/_technique_upgrade.html and then check if it fixes the issue ?
Thank you !
Updated by Mike Kingsbury about 6 years ago
- Status changed from New to Rejected
Ok, I missed that step as being required in the upgrade. Works as expected after that. Thanks.
-mike