Hide Forgot
Created attachment 1193561 [details] Register a system by Stage Customer Portal WebUI Description of problem: If I register a system by stage customer portal, the system can be registered and attach a subscription normally, but if I check the register info by subscription-manager CLI, it will show the system is not registered. Version-Release number of selected component (if applicable): subscription-manager-1.17.10-1.el7.x86_64 Stage Customer Portal: https://access.stage.redhat.com/management/consumers/ How reproducible: 100% Steps to Reproduce: 1.Log into Stage Customer Portal, open Systems->All Units->Register a unit, fill in all the options based on host system and register. please refer to the attached file[1] 2. Check the system is registered or not by WebUI, if registered, try to add a subscription for it please refer to the attached file[2] 3. Check the registered system by subscription-manager # subscription-manager refresh This system is not yet registered. Try 'subscription-manager register --help' for more information. # subscription-manager identity This system is not yet registered. Try 'subscription-manager register --help' for more information. Actual results: Subscription-manager shows the system is not registered even it's registered successfully by WebUI. Expected results: The system can be registered by WebUI and Subscription-manager CLI Additional info:
Created attachment 1193563 [details] Check register and subscribe status by WebUI
This is working as designed. The consumer identity has to be downloaded from the portal and installed on the system after the registration on the portal. Please see section "3.10.2. Workflow" of the following document for more information. It looks as though you are missing step 3 of the workflow below. https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html-single/Subscription_Concepts_and_Workflows/index.html If this does not help please update your reproduction steps and reopen the bug.
Have tried following the workflow on rhel7.3 and rhel6.9, both succeed, so the bug is not a bug.