community.general/changelogs/fragments/lxd-instance-not-found-avoid-false-positives.yml

minor_changes:
  - "lxd connection plugin - tighten the detection logic for lxd ``Instance not found`` errors, to avoid false detection on unrelated errors such as ``/usr/bin/python3: not found`` (https://github.com/ansible-collections/community.general/pull/7521)."
Lxd instance not found fix false positives (#7521) * lxd: Add lxc command execution debug statement. * lxd: avoid false positives in "instance not found" detection Due to changes over time in the error message which lxd printed when an instance wasn't found, the detection logic in the lxd connection plugin matched any "not found" string. Unfortunately this also false triggered on other errors e.g. "/usr/bin/python3: not found" from the payload, giving a confusing error message "UNREACHABLE! ... instance not found" to the ansible user. * Update changelog fragment. --------- Co-authored-by: Felix Fontein <felix@fontein.de> 2023-12-03 09:41:04 +01:00			`minor_changes:`
			- "lxd connection plugin - tighten the detection logic for lxd ``Instance not found`` errors, to avoid false detection on unrelated errors such as ``/usr/bin/python3: not found`` (https://github.com/ansible-collections/community.general/pull/7521)."