Clark Boylan a9a2f5ab50 Be more cautious initing mimetypes ... We use mimetypes to set file mime types for upload to log server locations. We also override yaml files mime type to text/plain when doing so. If we then call mimetypes.init() again this overrides the previous yaml update to text/plain. This wasn't a problem until python3.12 but python3.12 (on Ubuntu Noble specifically) seems to import test cases in a different order which results in the mimetypes.init() call in generate_manifest.py overriding the yaml mimetype set by the log upload test cases. Simply check if mimetypes is already inited before we init it again which should avoid the problem entirely. Note that this is likely to only ever by a testing issues as typically ansible wouldn't import all of this code together but the unittest runner does. Change-Id: Ifb9137ddd89713cad546129c462ad94315100940		2024-06-26 15:07:32 -07:00
..
test-fixtures	Use urlencoded filenames in test fixtures	2021-01-20 08:37:26 +01:00
__init__.py	Test role for upload-logs-swift	2019-10-11 11:32:11 -07:00
delete_container.py	Remove shebang from all python ansible modules	2022-09-15 13:48:10 -07:00
filefixture.py	Use urlencoded filenames in test fixtures	2021-01-20 08:37:26 +01:00
test_zuul_swift_upload.py	Use urlencoded filenames in test fixtures	2021-01-20 08:37:26 +01:00
zuul_swift_upload.py	Be more cautious initing mimetypes	2024-06-26 15:07:32 -07:00