Created attachment 1690089 [details]
output of the job run with some debugs added, most importantly on "sat_org_subscriptions.json"

Description of problem:
"Configure Cloud Connector" sometimes finds incorrect account, because it takes `sat_org_subscriptions.json | json_query('results[0].account_number')` and in my case `results[0]` is custom subscription which do not have account number.


Version-Release number of selected component (if applicable):
satellite-6.7.0-7.el7sat.noarch
ansiblerole-satellite-receptor-installer-0.6.4-1.el7sat.noarch
tfm-rubygem-foreman_rh_cloud-1.0.4.1-2.el7sat.noarch
python3-receptor-satellite-1.0.1-1.el7sat.noarch
receptor-0.6.1-1.el7ar.noarch


How reproducible:
always on my setup


Steps to Reproduce:
1. I had Receptor working
2. I deleted manifest and uploaded new one
3. Somewhere in the process (before or after uploading new manifest), I have created few custom products and repos
4. I reran "Configure Cloud Connector" playbook

But maybe you can also reproduce with creating a custom product on clean satellite/organization before you upload manifest and run "Configure Cloud Connector" - hopefully this will position custom product on a first position of `results` array in that API response


Actual results:
Account is detected as null, which causes rest of the playbook to not do what is expected - see attached output with debug on variable "sat_org_subscriptions.json" that should the problem clear (first item in `results` do not have account, second do)


Expected results:
Account should be detected correctly, even if first `results` item have null account