Bug Description

While the verification of OSPRH-19530 (that sets nbthread as 2) we could not find nbthread sub-string logged anywhere and also the full ovn metadata agent log on any node, container/pod.

Using an autohold of component job, but also looked in all fetched logs of recent successful`component-network-edpm-rhel9-rhoso18.0-crc` and could not find the file/log entry.

Issue possibly since some services on computes started logging to journal instead of containers.

To Reproduce Steps to reproduce the behaviour:

1. Deploy autohold of `component-network-edpm-rhel9-rhoso18.0-crc`.
2. Look for a known log entry within all files contents on nodes, or expected filename pattern (as in commands below).
3. Some of the attempted search commands on nodes and pods include:

sudo journalctl -u edpm_ovn_metadata_agent.service | grep "nbthread"
sudo journalctl | grep nbthread
sudo grep -IErin nbthread / 2>/dev/null
sudo find / -iname "*metadata*log*" 2>/dev/null