ansible/changelogs/fragments/70244-selinux-special-fs.yml

bugfixes:
  - Fix bytestring vs string comparison in module_utils.basic.is_special_selinux_path() so that special-cased filesystems which don't support SELinux context attributes still allow files to be manipulated on them. (https://github.com/ansible/ansible/issues/70244)
[stable-2.10] Fix string/bytestring comparsion in m_u.basic (#70439) (#73129) Change: - module_utils.basic.is_special_selinux_path() used a string == bytestring comparison which returned False and made Ansible think that certain filesystems aren't, in fact, special-cased, when they should be. Ensure both sides of the == are bytestrings. Test Plan: - Added `copy` integration tests for this case. Tickets: - Fixes #70244 Signed-off-by: Rick Elrod <rick@elrod.me>. (cherry picked from commit 688cd8657bcd4610aa268913be67e76778bc6940) 2021-01-11 07:55:15 +01:00			`bugfixes:`
			`- Fix bytestring vs string comparison in module_utils.basic.is_special_selinux_path() so that special-cased filesystems which don't support SELinux context attributes still allow files to be manipulated on them. (https://github.com/ansible/ansible/issues/70244)`