AWS EE build fails

[cloin]

@IPvSean looks like this EE build fails since this commit 08a645c

+ /usr/bin/microdnf install -y --nodocs --setopt install_weak_deps=0 dnf gcc krb5-devel libssh-devel python3-Cython python3-devel python39-devel unzip

(microdnf:45): librhsm-WARNING **: 00:51:36.377: Found 0 entitlement certificates

(microdnf:45): librhsm-WARNING **: 00:51:36.381: Found 0 entitlement certificates
Downloading metadata...
Downloading metadata...
Downloading metadata...
error: No package matches 'python39-devel'
time="2023-09-03T00:51:37Z" level=error msg="error unmounting container: error saving updated state for build container \"\": container not known"
Error: error building at STEP "RUN /output/scripts/assemble": error while running runtime: exit status 1

An error occurred (rc=125), see output line(s) above for details.

Error here: https://github.com/cloin/ee-builds/actions/runs/6061470857/job/16446713494#step:7:388

[sean-m-sullivan]

Got this same error elsewhere including the workshops, Use Rhel8 images and its good, something in the base rhel9 images doesn't jive.

[anshulbehl]

Looks like there is an issue with current version of certified redhat.sso collection's bindeps, which is causing the install of python39-devel in the EE, this is fixed upstream so a version update on hub should fix this. Until that time, the fix for the EE is

build_arg_defaults:
  EE_BASE_IMAGE: 'registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel9'
  EE_BUILDER_IMAGE: 'registry.redhat.io/ansible-automation-platform-24/ansible-builder-rhel9'

if the minimal EE can work as the base layer as opposed to supported
cc: @IPvSean

[nleiva]

Oh... I also run into this. The culprit seems to be redhat.sso requiring an rpm that's not available on RHEL9.

'python39-devel [platform:rpm compile]  # from collection redhat.sso'