Hi Lee, > This is generally not supported, I've explained the rationale here: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111137#10 > > I don't think we should deviate from the support matrix provides by upstream,
I understand the motivation. Extra link for others coming to this: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix However, we cannot just upgrade the control node quite yet as there are a handful buster systems still (working on upgrading these) and even a few stretch systems (that may need to live a while longer), which the bookworm ansible-core still supports. > as I expect a few dozen bugs when running against trixie hosts. OK. This is the only one I’ve run into so far, and I solved it by adding the two-line patch into the file in /usr locally. I’ll take your info and rationale with me and we’ll be finding some solution (perhaps something that skips running on old hosts if the repo playbooks are run on the new control node, viceque versa; there has to be something (I’m new to ansible) that makes this possible). Thanks, //Thorsten -- Thorsten Glaser Linux / Unix Developer Tel.: +49 160 91168501 E-Mail: [email protected] B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / https://www.b1-systems.de/ GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537
