Bug 1304074
| Summary: | [RFE] Provide a D-Bus API for Registering a system | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Barnaby Court <bcourt> | ||||||
| Component: | subscription-manager | Assignee: | Alex Wood <awood> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Sean Toner <stoner> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.3 | CC: | csnyder, khowell, stoner | ||||||
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-01 19:18:42 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1313485, 1395274 | ||||||||
| Attachments: |
|
||||||||
|
Description
Barnaby Court
2016-02-02 19:45:20 UTC
I manually tested by doing the following:
Created a stage account, and edit the /etc/rhsm/rhsm.conf to point to the stage candlepin. I also generated an activation key from the stage customer portal. I
I then ran `systemctl restart rhsm.service` and then ran `subscription-manager orgs` to get the org ID. I made sure that the dbus service was running by calling:
busctl | grep RHSM
and verified that the service was running and not activatable. I then did the first part of registering by starting the register server:
busctl call com.redhat.RHSM1 /com/redhat/RHSM1/RegisterServer com.redhat.RHSM1.RegisterServer Start
This gave me the reply back of:
s "unix:abstract=/var/run/dbus-hFLSsUWi7q,guid=1cc8ab09c9c716d9f755819358f50415"
This response provided the unix socket ID of "unix:abstract=/var/run/dbus-hFLSsUWi7q", which is necessary for the other busctl calls. Since the register server now had a unix socket to communicate over (a peer-to-peer), the call to actually do the registering was done as below:
busctl call --address=unix:abstract=/var/run/dbus-hFLSsUWi7q com.redhat.RHSM1 /com/redhat/RHSM1/Register com.redhat.RHSM1.Register Register 'sssa{sv}' 10930238 BZ1304074 ________ 0
The 10930238, BZ1304074 and _______ are the org, username and password respectively. The result of running the above command can be seen in the attachment Register.txt. Lastly, I also tested registering via an activation key. The command to do this was:
busctl call --address=unix:abstract=/var/run/dbus-hFLSsUWi7q com.redhat.RHSM1 /com/redhat/RHSM1/Register com.redhat.RHSM1.Register RegisterWithActivationKeys 'sasa{sv}' 10930238 1 BZ1304074-Key 0
Where "10930238 1 BZ1304074-Key 0" is the encoding for dbus args using busctl where I passed in just one activation key with a name of BZ1304074-Key, and no extra args were used for registration. The result of this command can be seen in the attachment RegisterWithKey.txt
Created attachment 1272141 [details]
using busctl to call Register method
Created attachment 1272142 [details]
using busctl to call RegisterWithActivationKeys method
Tested against: [root@stoner-rhel-74 subman1.9.7]# rpm -qa | grep subscription subscription-manager-1.19.7-1.el7.x86_64 subscription-manager-plugin-container-1.19.7-1.el7.x86_64 subscription-manager-migration-data-2.0.35-1.el7.noarch subscription-manager-plugin-ostree-1.19.7-1.el7.x86_64 subscription-manager-migration-1.19.7-1.el7.x86_64 subscription-manager-initial-setup-addon-1.19.7-1.el7.x86_64 subscription-manager-gui-1.19.7-1.el7.x86_64 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/RHBA-2017:2083 |