Description
Describe the bug
Hello all,
I was excited for Anomalib v2 release for several months now and I have run into the dreaded FATAL FIPS SELFTEST FAILURE. I am required to work on FIPS enabled devices and this forces certain security practices. I am now unable to use Anomalib v2 as a package.
I have been able to replicate this on multiple machines in my office. I've experienced this with other libraries, and the only fix I have found is to clone the repo, don't install it, and run it as code. Unfortunately, I haven't quite figured out what causes this and the appropriate way to solve it. I am willing to attempt to fix this, but I would need guidance in where to start.
I really hope this can be resolved as Anomalib has been superb in our work.
Dataset
N/A
Model
N/A
Steps to reproduce the behavior
- Enable FIPS on your device.
- Create your env and install anomalib
- Create python file and add the following line:
from anomalib.data import Folder
- Run python file.
OS information
OS information:
- OS: RHEL 9.5
- Python version: 3.11
- Anomalib version: 2
- PyTorch version: 2.6
- CUDA/cuDNN version: 12.6
- GPU models and configuration: 8x RTX 4090
- Any other relevant information: FIPS Enabled
Expected behavior
Expected to work as intended.
Screenshots
No response
Pip/GitHub
pip
What version/branch did you use?
No response
Configuration YAML
N/A
Logs
N/A
Code of Conduct
- I agree to follow this project's Code of Conduct