Dear TRex community
I am reaching out to you as I have encountered an issue while running a privileged pod with the TRex application (v3.02).
Issue Description:
I'm running a privileged pod on a OCP4.13 cluster. The pod is running this TRex command and failing on this error:
```
# ./t-rex-64 --no-ofed-check --no-hw-flow-stat -i -c 6 --iom 0
...
Starting Scapy server..... Scapy server failed to run
Output: b'Traceback (most recent call last):\n File "/usr/lib64/python3.9/runpy.py", line 197, in _run_module_as_main\n return _run_code(code, main_globals, None,\n File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code\n exec(code, run_globals)\n File "/opt/trex/automation/trex_control_plane/interactive/trex/scapy_server/scapy_zmq_server.py", line 198, in <module>\n sys.exit(main(args,port))\n File "/opt/trex/automation/trex_control_plane/interactive/trex/scapy_server/scapy_zmq_server.py", line 185, in main\n s = Scapy_server(args,port)\n File "/opt/trex/automation/trex_control_plane/interactive/trex/scapy_server/scapy_zmq_server.py", line 102, in __init__\n self.scapy_wrapper = Scapy_wrapper()\n File "/opt/trex/automation/trex_control_plane/interactive/trex/scapy_server/scapy_zmq_server.py", line 26, in __init__\n self.scapy_master = Scapy_service()\n File "/opt/trex/automation/trex_control_plane/interactive/trex/scapy_server/scapy_service.py", line 467, in __init__\n self.server_v_hashed = self._generate_version_hash(self.version_major,self.version_minor)\n File "/opt/trex/automation/trex_control_plane/interactive/trex/scapy_server/scapy_service.py", line 820, in _generate_version_hash\n m = hashlib.md5()\nValueError: [digital envelope routines] unsupported\n'
WARNING: tried to configure 2048 hugepages for socket 0, but result is: 0
WARNING: tried to configure 2048 hugepages for socket 1, but result is: 0
Could not start scapy daemon server, which is needed by GUI to create packets.
If you don't need it, use --no-scapy-server flag.
ERROR encountered while configuring TRex system
```
Using the trex verbose "-v 6" flag did not give me additional information.
Also attaching the trex_cfg.yaml and the full command log.
Interestingly, when I run the same pod image on OCP4.12, the issue does not occur.
I would greatly appreciate any assistance or guidance you can provide in resolving this problem. If you require any additional information or context to better understand the problem, please do not hesitate to ask.
Thank you in advance for your assistance and support.
Best regards,