JK Laiho

This issue is still present in 2.1.1.0. The same error also happens if I'm trying to activate pipelining on a task-by-task-basis using: ``` - name: some task ... vars: ansible_ssh_pipelining:...

@jctanner Tried this just now with Ansible v2.2.1.0. The results of the various combinations: `sudo_flags, pipelining, ssh_args`: ❌ `sudo_flags, pipelining`: ❌ `pipelining, ssh_args`: ✅ `pipelining`: ✅ `sudo_flags, ssh_args`: ✅ So...

@jctanner Just for kicks, I tried to manually run the command that is printed out on the `SSH: EXEC` row in my last comment: ``` $ sudo -i -p "[sudo...

Added the component name section to the issue, as requested.

I'm seeing the same thing. While deploying a Ubuntu 22.04 server, I downloaded https://github.com/containers/conmon/releases/download/v2.1.3/conmon.amd64, and am unable to use `log_driver="journald"` in `containers.conf` with it. Seems related to https://github.com/containers/podman/issues/5467

In the logs, here's what a successful PUT request to for the Resolve and Auto-Assign setting looked like: ``` sentry-self-hosted-web-1 | 13:54:12 [INFO] sentry.superuser: superuser.request (url='http://sentry.somedomain.com/api/0/users/me/notifications/' method='PUT' ip_address='x.x.x.x' user_id=5) sentry-self-hosted-web-1...

The Email Routing subpage is the only one that works. The API call done as a result of loading it is to `/api/0/users/me/notifications/email/`, returning HTTP 200. Every other subpage's API...

To add to the previous comment, the only thing that comes to mind that could be different between two self-hosted installations is if some configurations related to these problems are...

> Do you remember a version of Sentry you were on that had this working before 23.11.2? That may give some clue into what is happening. No, I don't think...

@scefali indeed, and given the information I've provided in earlier comments, it's not at all clear how this could be the case. Two theoretical options come to mind: 1. While...