Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
Hi Lukáš,
It is proposed for both releases. The ON_QA is for 6.8 (Target Milestone = 6.8.0). If the BZ is selected for the zstream during zstream triage, it will be 'cloned' for a specific 6.7.z and then Target Milestone set (e.g. 6.7.2).
thanks,
Brad
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