If a user mistakenly publishes a collection that already exists in Private Automation Hub and the collection has the same version information, then an error appears when attempting to approve the collection in the Private Automation Hub Approval screen which normally moves a collection from the staged repository to the published repository. For example, the following is a duplicate version of the ansible posix v2.0.0 collection that had been uploaded and this is the error message that appears in the UI when trying to approve the collection:

Changes to certification status for collection "ansible posix v2.0.0" could not be saved.
Error 404 - Not Found: The server could not find the requested URL.

You can also see the error in the Private Automation Hub server /var/log/messages directory:

May 12 11:34:50 example_host pulpcore-api[412891]: pulp [0dba18feb7614ebe94de27845cbedead]: django.request:WARNING: Not Found: /api/galaxy/v3/collections/ansible/posix/versions/2.0.0/move/staging/published/

There is no workaround for this problem because Private Automation Hub doesn't overwrite identical collections during the approval process. For more information about enabling and disabling the approvals function when uploading collections, see the chapter about configuring the parameter file in Oracle Linux Automation Manager 2.3: Private Automation Hub Installation Guide. If the approvals olpah_require_content_approval: False function disabled using the olpah_require_content_approval: False parameter, this message doesn't appear because the collection goes directly into the published repository.

When running a job template with a custom execution environment built on Oracle Linux 9, the following deprecation warning might appear:

Identity added: /runner/artifacts/36/ssh_key_data (/runner/artifacts/36/ssh_key_data)
/usr/local/lib/python3.9/site-packages/paramiko/pkey.py:82: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from cryptography.hazmat.primitives.ciphers.algorithms in 48.0.0.
  "cipher": algorithms.TripleDES,
/usr/local/lib/python3.9/site-packages/paramiko/transport.py:253: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from cryptography.hazmat.primitives.ciphers.algorithms in 48.0.0.
  "class": algorithms.TripleDES,

When creating a custom execution environment with the builder utility using Oracle Linux 9, the following error or warning message might appear relating to potential scenarios where systemd session is already actively running:

sd-bus call: Interactive authentication required.: Permission denied

or

WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to log in using a user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1001` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs

A workaround for this problem is to set the following loginctl user setting before logging into the user account:

sudo loginctl enable-linger <user_name>

The download bundle function on the topology viewer feature returns the following error message:

"A server error has occurred."

This issue is being investigated.