Description of problem: Failed to auto-attach RHEL-8.0-Snapshot-1.0 against Satellite6.4 Version-Release number of selected component (if applicable): subscription-manager-1.23.8-1.el8.x86_64 katello-3.7.0-8.el7sat.noarch tfm-rubygem-katello-3.7.0.41-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. Install RHEL-8.0-20181120.0, and register it to Satellite6.4: [root@dell-r730-001-guest15 ~]# subscription-manager register Registering to: ent-01-vm-02.lab.eng.nay.redhat.com:443/rhsm Username: admin Password: The system has been registered with ID: c65add8d-b5a8-4251-9153-2e6f46230076 The registered system name is: dell-r730-001-guest15.dsal.lab.eng.rdu2.redhat.com 2. Run auto-attach: [root@dell-r730-001-guest15 ~]# subscription-manager attach HTTP error code 500: Runtime Error TypeError: Cannot read property "length" from undefined (rules#2982) at org.mozilla.javascript.ScriptRuntime.constructError:3,785 3. Check the manifest: 1) Manifest is imported into Satellite. 2) Delete the manifest on Satellite Web UI, and re-import it: Manifes can be re-imported with an error 'Validation failed: Locations expecting locations used by hosts or inherited (check mismatches report).' Actual results: As step 2. Expected results: Auto-attach should be successful. Manifest should be imported into satellite6.4 successfully. Additional info: I'm not sure if the auto-attach failure is related to the manifest importing error. But I attach all the related attachments here: Please see attachment 'rhsm.log' on RHEL8. Please see attachments 'manifest-import-error.png', 'manifest-import-task.png', and 'manifest-import-error-details' on Satellite Web UI.
Created attachment 1507870 [details] manifest-import-error.png
Created attachment 1507871 [details] manifest-import-task.png
Created attachment 1507872 [details] rhsm.log
Created attachment 1507873 [details] manifest-import-error-details
k-attach-subscription is the wrong component for this, moving to registration
Please confirm if the original registration attempt was in the stage environment.
This is my timeline, as I understand it: 2018-11-14 - Stage upgraded to Candlepin 2.3.10 2018-11-21 - This bug is filed 2018-11-28 - Stage downgraded to Candlepin 2.3.9 - jsefler noted that auto-attaching subs (not relating to Satellite) fails. - I deleted the rules that came with Candlepin 2.3.10, reverting back to 2.3.9 rules - auto-attaching works again How I see it, this is potentially an issue with the rules that came with 2.3.10.
Hi Jenny and Shayne, I used Ethel to create an account, and attach related SKUs. Then I logged in the Stage Customer Portal to export manifest for Satellite6.4. I don't know when the Stage candlepin was upgraded from 2.3.9 to 2.3.10, but my manifest for Satellite is not exported during recent days. Hope my information can help.
(In reply to Tramaine Darby from comment #9) > Please confirm if the original registration attempt was in the stage > environment. Yes, Tramaine, I use Stage environment to export my manifest. Can I understand it like this: Although manifest have been exported from Stage, the change of Stage candlepin will affect entitlement consuming through the manifest?
Created attachment 1510064 [details] task_warning_when_importing_latest_manifest.png
Today(Nov 30 CST 2018), I deployed a totally new Satellite6.4.0, and exported the latest manifest from Stage for Satellite6.4. Then register RHEL-8.0-20181120.0 against Satellite6.4.0, and auto-attach: 1) Satellite6.4.0: tfm-rubygem-katello-3.7.0.41-1.el7sat.noarch candlepin-2.4.8-1.el7.noarch 2) RHEL-8.0-20181120.0: [root@dell-r730-001-guest27 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 3.7.0.41-Unknown subscription management rules: 5.26 subscription-manager: 1.23.8-1.el8 3) [root@dell-r730-001-guest27 ~]# subscription-manager register Registering to: ibm-x3655-03.ovirt.rhts.eng.bos.redhat.com:443/rhsm Username: admin Password: The system has been registered with ID: bc64fa73-163b-407c-abd4-4d562388afdc The registered system name is: dell-r730-001-guest27.dsal.lab.eng.rdu2.redhat.com [root@dell-r730-001-guest27 ~]# subscription-manager attach Installed Product Current Status: Product Name: Red Hat Enterprise Linux for x86_64 High Touch Beta Status: Subscribed
(In reply to qianzhan from comment #17) > Today(Nov 30 CST 2018), I deployed a totally new Satellite6.4.0, and > exported the latest manifest from Stage for Satellite6.4. > > Then register RHEL-8.0-20181120.0 against Satellite6.4.0, and auto-attach: > > 1) Satellite6.4.0: > > tfm-rubygem-katello-3.7.0.41-1.el7sat.noarch > candlepin-2.4.8-1.el7.noarch > > 2) RHEL-8.0-20181120.0: > [root@dell-r730-001-guest27 ~]# subscription-manager version > server type: Red Hat Subscription Management > subscription management server: 3.7.0.41-Unknown > subscription management rules: 5.26 > subscription-manager: 1.23.8-1.el8 > > 3) > [root@dell-r730-001-guest27 ~]# subscription-manager register > Registering to: ibm-x3655-03.ovirt.rhts.eng.bos.redhat.com:443/rhsm > Username: admin > Password: > The system has been registered with ID: bc64fa73-163b-407c-abd4-4d562388afdc > The registered system name is: > dell-r730-001-guest27.dsal.lab.eng.rdu2.redhat.com > > > [root@dell-r730-001-guest27 ~]# subscription-manager attach > Installed Product Current Status: > Product Name: Red Hat Enterprise Linux for x86_64 High Touch Beta > Status: Subscribed Move this bug to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222