Description of problem: When running rhn-check on a client running Fedora messages of the form: Updated system release from 24 to 24 The Red Hat Satellite Update Agent has detected a change in the base version of the operating system running on your system, additionaly you are subscribed to a custom channel as your base channel. Due to this configuration your channel subscriptions will not be altered. are created in the logs. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. run rhn-check on a fedora host 2. Browse to the history events of a system Actual results: Client: [root@provisioner rhn]# rhn_check -vvvvv D: opening db environment /var/lib/rpm cdb:0x401 D: opening db index /var/lib/rpm/Packages 0x400 mode=0x0 D: locked db index /var/lib/rpm/Packages D: opening db index /var/lib/rpm/Providename 0x400 mode=0x0 D: rpcServer: Calling XMLRPC registration.upgrade_version D: do_call packages.checkNeedUpdate('rhnsd=1',){} D: Called refresh_rpmlist Updating package profile D: rpcServer: Calling XMLRPC registration.welcome_message D: rpcServer: Calling XMLRPC registration.update_packages D: local action status: (0, 'rpmlist refreshed', {}) D: rpcServer: Calling XMLRPC registration.welcome_message D: closed db index /var/lib/rpm/Packages D: closed db index /var/lib/rpm/Providename D: closed db environment /var/lib/rpm XMLRPC Log on the server: 2016/09/28 02:04:13 -00:00 7664 10.7.8.30: xmlrpc/registration.upgrade_version(1000010002, '23') 2016/09/28 02:04:13 -00:00 7665 10.7.8.30: xmlrpc/queue.get(1000010002, 2, 'checkins enabled') 2016/09/28 02:04:13 -00:00 7666 10.7.8.30: xmlrpc/registration.welcome_message('lang: None',) 2016/09/28 02:05:24 -00:00 8201 10.7.2.42: xmlrpc/registration.upgrade_version(1000010000, '24') 2016/09/28 02:05:24 -00:00 7972 10.7.2.42: xmlrpc/queue.get(1000010000, 2, 'checkins enabled') 2016/09/28 02:05:25 -00:00 7664 10.7.2.42: xmlrpc/registration.welcome_message('lang: None',)
Closing as duplicate of bug 1397308, steps to reproduce this bug and results are the same. The resolution will be mentioned in BZ#1397308. *** This bug has been marked as a duplicate of bug 1397308 ***
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.