Bug 947788 - Migration failed with error “sending dbus signal with message: post_facts_collection”
Summary: Migration failed with error “sending dbus signal with message: post_facts_col...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 5.10
Assignee: Adrian Likins
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel510 rhsm-2013
TreeView+ depends on / blocked
 
Reported: 2013-04-03 09:11 UTC by spandey
Modified: 2015-04-23 23:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
No description necessary
Clone Of:
Environment:
Last Closed: 2013-09-30 23:05:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhsm.log output (20.66 KB, text/x-log)
2013-04-03 09:11 UTC, spandey
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1332 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2013-09-30 22:49:24 UTC

Description spandey 2013-04-03 09:11:07 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
2/2

Prerequisites:
Rhel6.4 with following subscription-manager rpm 
subscription-manager-migration-data-1.12.2.6-1.git.0.171d4c3.el6.noarch
subscription-manager-firstboot-1.8.5-1.git.4.82e4aee.el6.x86_64
subscription-manager-gui-1.8.5-1.git.4.82e4aee.el6.x86_64
subscription-manager-1.8.5-1.git.4.82e4aee.el6.x86_64
subscription-manager-migration-1.8.5-1.git.4.82e4aee.el6.x86_64

Steps to Repro : 
Register client to rhn_classic .
Migrate client from rhn_classic to certificate based system .

Expected Result : 
Client should migrate from classic to rhm no error message should display on console .

Actual Result : 
[root@dhcp193-132 ~]# rhn-migrate-classic-to-rhsm 
Red Hat account: qa
Password: 

Retrieving existing RHN Classic subscription information...

+-----------------------------------------------------+
System is currently subscribed to these RHN Classic Channels:
+-----------------------------------------------------+
rhel-x86_64-server-6

+-----------------------------------------------------+
Installing product certificates for these RHN Classic channels:
+-----------------------------------------------------+
rhel-x86_64-server-6

Product certificates installed successfully to /etc/pki/product.

Preparing to unregister system from RHN Classic...
System successfully unregistered from RHN Classic.

Attempting to register system to Red Hat Subscription Management...
sending dbus signal with message: post_facts_collection
[Errno 2] No such file or directory

Unable to register.
For further assistance, please contact Red Hat Global Support Services.

Comment 1 spandey 2013-04-03 09:11:50 UTC
Created attachment 731064 [details]
rhsm.log output

Comment 2 RHEL Program Management 2013-04-09 20:15:43 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 3 Adrian Likins 2013-06-05 17:43:14 UTC
proposed fix at https://github.com/candlepin/subscription-manager/pull/634

(or, install 'facter' package or uninstall example plugins)

Comment 4 Adrian Likins 2013-06-13 17:36:33 UTC
in master, will be in 1.8.11 or newer

commit 0eea7f54a0ed21f219cc9b0c8d0836f7f27cc9d9
Author: Adrian Likins <alikins>
Date:   Wed Jun 5 13:39:08 2013 -0400

    947788: facts plugin can handle no 'facter'
    
    Before the example facts plugin assumed if you
    installed it, that 'facter' would be installed.
    
    Add some robustness to it's proccess handling.

Comment 6 John Sefler 2013-07-03 19:20:29 UTC
Verifying Version...
[root@rhsm-compat-rhel64 ~]# rpm -q subscription-manager-migration
subscription-manager-migration-1.8.11-1.el6.x86_64


[root@rhsm-compat-rhel64 ~]# rhnreg_ks --serverUrl=https://xmlrpc.rhn.code.stage.redhat.com/XMLRPC --username=qa --password=*****
[root@rhsm-compat-rhel64 ~]# rhn-channel --list
rhel-x86_64-server-6
[root@rhsm-compat-rhel64 ~]# rhn-migrate-classic-to-rhsm --serverurl subscription.rhn.stage.redhat.com
Red Hat account: qa
Password: 
System Engine Username: qa
Password: 

Retrieving existing RHN Classic subscription information...

+-----------------------------------------------------+
System is currently subscribed to these RHN Classic Channels:
+-----------------------------------------------------+
rhel-x86_64-server-6

+-----------------------------------------------------+
Installing product certificates for these RHN Classic channels:
+-----------------------------------------------------+
rhel-x86_64-server-6

Product certificates installed successfully to /etc/pki/product.

Preparing to unregister system from RHN Classic...
System successfully unregistered from RHN Classic.

Attempting to register system to Red Hat Subscription Management...
The system has been registered with ID: 34581088-d51b-4eae-ab25-0c36cd3f3d05 
System 'rhsm-compat-rhel64.usersys.redhat.com' successfully registered to Red Hat Subscription Management.

Attempting to auto-attach to appropriate subscriptions...
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status:       Not Subscribed


Unable to auto-attach.  Do your existing subscriptions match the products installed on this system?

Please visit https://access.redhat.com/management/consumers/34581088-d51b-4eae-ab25-0c36cd3f3d05 to view the details, and to make changes if necessary.
[root@rhsm-compat-rhel64 ~]# 


VERIFIED: registration was successful without post_facts_collection errors

Additional Note: the failure to autosubscribe is due to bug 977321

Comment 8 errata-xmlrpc 2013-09-30 23:05:33 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-1332.html


Note You need to log in before you can comment on or make changes to this bug.