Bug 767798 - Last check in shows Never Checked In
Summary: Last check in shows Never Checked In
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent vote
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 760591
Blocks: 703617 katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-12-14 22:00 UTC by Tom McKay
Modified: 2014-09-18 15:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 760591
Environment:
Last Closed: 2012-04-27 00:32:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Tom McKay 2011-12-14 22:00:22 UTC
+++ This bug was initially created as a clone of Bug #760591 +++

Description of problem:
Even after hours or days a registered+subscribed system will still show Never Checked In on the Systems page of headpin.

Version-Release number of selected component (if applicable):
katello-headpin-all-0.1.111-1.el6.noarch

Steps to Reproduce:
1. Register + Subscribe a system
2. Restart rhsmcertd on the registered consumer
3. Run subscription-manager refresh
4. Go to https://headpin.fqdn/headpin
5. Navigate to the systems page
  
Actual results:
Note that under System Events, Checked In remains "Never Checked In".

Expected results:
A date / time stamp of last check in.

Comment 1 Jesus M. Rodriguez 2011-12-16 20:52:08 UTC
Katello is sending cp-user as the OAuth header for both user and consumer level access. This means that when rhsmcertd runs in step 2, katello is connecting to candlepin as a TrustedUserPrincipal which is NOT a ConsumerPrincipal hence there is no lastcheckin to update. 

We changed line 322 of user.rb to be self.current.cp_oauth_header instead of 
{ 'cp-user' => self.current.username }

That one change makes katello talk to candlepin with the correct headers,
and users i.e. TrustedUserPrincipal and TrustedConsumerPrincipal.

Comment 2 Bryan Kearney 2011-12-19 13:51:52 UTC
Fixed in katello commit dd8719985c6c475741cd5edd0e448827b51809f9. You will need to wait for katello-commmon 0.147 to see this fix.

Comment 3 Eric Sammons 2011-12-20 15:22:04 UTC
Verified

Comment 5 Mike McCune 2013-08-16 18:24:35 UTC
getting rid of 6.0.0 version since that doesn't exist


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