Hide Forgot
Description of problem: Recent state of CLI `system register` is not in a good shape right now: it *does* registers the system to katello, but the rest of the details are not correctly collected. Attached is some illustration of that. (system registered via: `system register --name cli-registered-system --org ACME_Corporation --environment test`) Version-Release number of selected component (if applicable): katello-configure-0.1.42-1.git.0.6e56b57.el6.noarch katello-0.1.148-1.git.0.0b9ff7d.el6.noarch katello-cli-0.1.29-1.git.0.e3ec54b.el6.noarch candlepin-0.5.8-1.el6.noarch pulp-0.0.255-1.el6.noarch How reproducible: always using CLI (shell) Steps to Reproduce: 1. see above. (self-registration also works ;)) 2. 3. Actual results: system is registered (RHEL) but in the UI details shows Fedora, with no IP info, almost no info in details, facts. Expected results: Full functionality as subscription-manager has Additional info:
The problem with cli system registration is that to fully support all the functionality of subscription-manager, it would need to generate the system facts for the system like subsription-manager does. But to get facts it must be executed on the registered machine - and therecan be used subscription manager directly. On of possible usecases for cli register would be to create a system and prepare subscriptions before the actual system is created and in registration phase use the following command: subscription-manager register --consumerid 12101860-7226-4684-8596-136c9b84d18
fixed in 2cb1361c8945388081d27fafdcfefd844ca6bc4a
*** Bug 733643 has been marked as a duplicate of this bug. ***
Moving all community bugs with fixes to closed.