Hub has OCP 4.14 with TALM, ACM 2.9. Attempting to deploy a OCP 4.14 SNO spoke with the DU profile results in policies never going Compliant.

On the spoke, the install plans show as Approval: Manual and State: false

$ oc get installplans.operators.coreos.com -A 
NAMESPACE                          NAME            CSV                                           APPROVAL   APPROVED
openshift-local-storage            install-cnnwn   local-storage-operator.v4.14.0-202309012142   Manual     false
openshift-logging                  install-gwdb9   cluster-logging.v5.8.0                        Manual     false
openshift-ptp                      install-mh6xh   ptp-operator.v4.14.0-202309142202             Manual     false
openshift-sriov-network-operator   install-2l7rr   sriov-network-operator.v4.14.0-202309120726   Manual     false
vran-acceleration-operators        install-mpgph   sriov-fec.v2.7.1                              Manual     false

This worked on pre rc0 build

###hub:

Originally same version as spoke.

Going to try a nightly to try to reproduce

$ oc get installplans.operators.coreos.com -A 
NAMESPACE             NAME            CSV                                        APPROVAL    APPROVED
multicluster-engine   install-v4vfs   multicluster-engine.v2.4.0-161             Automatic   true
openshift-operators   install-dx5d5   topology-aware-lifecycle-manager.v4.14.0   Automatic   true
openshift-operators   install-mhjv4   openshift-gitops-operator.v1.9.2           Automatic   true
rhacm                 install-fszbv   advanced-cluster-management.v2.9.0-140     Automatic   true

ztp-site-generator:v4.14.0-59

For TALM:
registry-proxy.engineering.redhat.com/rh-osbs/openshift4-topology-aware-lifecycle-manager-operator-bundle-container-rhel8@sha256:9a773c38954c655390cddfd7be709b305fad508475e2ceb550a98fb2608c7861
skopeo: https://access.redhat.com/containers/#/registry.access.redhat.com/openshift4/topology-aware-lifecycle-manager-operator-bundle-container-rhel8/images/v4.14.0-58

###spoke: 
version   4.14.0-rc.0   True        False         35m     Cluster version is 4.14.0-rc.0
Spoke never successfully deploys, so oc commands timeout
 

Always

1. Deploy hub
2. Deploy spoke using vRAN deployment Jenkins job
3.

install plans are not approved, so policies never reconcile and cgu times out waiting for policies.

install plans have automatic approval

Workaround is the manual set the installplans to approved: true in time before cgu times out waiting for policies to be Compliant.

hub must-gather and spoke journalctl logs attached in comments