Bug 1198464

Summary: Katello needs to activate pulp consumer as node
Product: Red Hat Satellite Reporter: Stephen Benjamin <stbenjam>
Component: Content ManagementAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Corey Welton <cwelton>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: aladke, bbuckingham, cwelton, jmontleo, omaciel
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9521
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:28:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Benjamin 2015-03-04 08:39:33 UTC
After chatting with jortel a pulp node needs to be activated using this method:

https://github.com/Katello/katello/blob/106bb48226f970a58b4329c6db3cd398477c49f1/app/models/katello/glue/pulp/consumer.rb#L202

when a capsule registers with the pulp_node feature.

from irc:


```
   jortel | stbenjam: looking at your node sync issue, you capsule does not seem to be   
          | activated as a node (in the pulp db)                                         
jsherrill | jortel: when you say 'activated' what do you mean exactly?                   
jsherrill | which api call?                                                              
   jortel | jsherrill: when you create the consumer, you need to add a special top-secret
          | note that indicates it's a node and what it's strategy is                    
   jortel | jsherrill: or, in a consumer update                                          
jsherrill | jortel: is this new?                                                         
jsherrill | (my memory is a little fuzzy)                                                
jsherrill | and i'm trying to find where we might have ever done that                    
jsherrill | i dont' see anything                                                         
jsherrill | we were just registering the consumer and adding environments to sync        
jsherrill | as far as i can tell                                                         
jsherrill | errr, adding repos                   
jsherrill | jortel: doesn't look like, it is possible pulp 2.4 didn't care? 
jortel    | jsherrill: yes, it's possible.  iirc, we fixed a bug whereby that strategy
         | was not being passed to the agent.                                        
```

my guess is that we used to call this method when pulp nodes were first implemented but that got lost along the way.

Comment 1 Stephen Benjamin 2015-03-04 08:39:36 UTC
Created from redmine issue http://projects.theforeman.org/issues/9521

Comment 6 Corey Welton 2015-03-18 12:54:43 UTC
Verified in Satellite-6.1.0-RHEL-7-20150311.1

Comment 7 Corey Welton 2015-03-18 12:56:56 UTC
*** Bug 1198405 has been marked as a duplicate of this bug. ***

Comment 8 Mike McCune 2015-07-09 21:07:37 UTC
*** Bug 1214308 has been marked as a duplicate of this bug. ***

Comment 9 Bryan Kearney 2015-08-11 13:18:10 UTC
This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:28:48 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.

https://access.redhat.com/errata/RHSA-2015:1592