Hide Forgot
Description of problem: function client_sudo_user_is_allowed() { su user1 -c "sudo -u user2 ${*-true}" } function client_sudo_user_is_denied() { { ! client_sudo_user_is_allowed "$@"; } } for ((i = 1; i<= 5; i++)); do server_rule_modify test <<<"\ replace: sudoUser sudoUser: user2" sleep "0" client_sudo_user_is_denied || { status=1; break; } server_rule_modify test <<<"\ replace: sudoUser sudoUser: user1" sleep "2" client_sudo_user_is_allowed || { status=1; break; } done :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: stress_refresh :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ BEGIN ] :: stress_refresh_attr_user :: actually running 'strict eval 'stress_attr User user2 0 user_is_denied user1 2 user_is_allowed'' user1 is not in the sudoers file. This incident will be reported. user1 is not in the sudoers file. This incident will be reported. user1 is not in the sudoers file. This incident will be reported. :: [ FAIL ] :: stress_refresh_attr_user (Expected 0, got 1) Version-Release number of selected component (if applicable): sssd-1.13.3-22.el6.s390x How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Pavel agreed he'd take a look.
This turned out to be a bug in tests. Closing.