** Description changed: + [ Impact ] + + * Ansible users cannot perform password-authenticated privilege + escalation on Ubuntu systems using sudo-rs. After entering the correct + become password, Ansible fails with "Timed out waiting for become + success or become password prompt". + + [ Test Plan ] + + * <TODO> + + [ Where problems could occur ] + + * The change affects sudo become password-prompt detection. Regressions + could cause missed prompts and timeouts, false recognition of unrelated + output, or incorrect repeated-password handling. + + * Changes do not and can't bypass sudo authentication. + + [ Other Info ] + + * Both commits for resolute are unchanged from the merged upstream pull + requests. + + --- + When using ansible with a site or a task using "become: yes", ansible will prompt for the password (forwarded to sudo) before running. When doing so with sudo-rs, after the password is provided by the user, ansible hangs and then throws the following error: "Timed out waiting for become success or become password prompt" When setting sudo.ws as the default with update-alternatives, ansible proceeds as expected after the password is provided. DistroRelease: Ubuntu 25.10 Package: ansible-core 2.19.0-1ubuntu1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122414 Title: Ansible times out after BECOME password request To manage notifications about this bug go to: https://bugs.launchpad.net/ansible/+bug/2122414/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
