Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1198464 - Katello needs to activate pulp consumer as node
Katello needs to activate pulp consumer as node
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
6.0.4
Unspecified Unspecified
unspecified Severity high (vote)
: Unspecified
: Unused
Assigned To: Justin Sherrill
Corey Welton
http://projects.theforeman.org/issues...
: Triaged
: 1198405 1214308 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-04 03:39 EST by Stephen Benjamin
Modified: 2017-02-23 15:23 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:28:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 9521 None None None 2016-04-22 11:11 EDT
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Stephen Benjamin 2015-03-04 03:39:33 EST
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 03:39:36 EST
Created from redmine issue http://projects.theforeman.org/issues/9521
Comment 6 Corey Welton 2015-03-18 08:54:43 EDT
Verified in Satellite-6.1.0-RHEL-7-20150311.1
Comment 7 Corey Welton 2015-03-18 08:56:56 EDT
*** Bug 1198405 has been marked as a duplicate of this bug. ***
Comment 8 Mike McCune 2015-07-09 17:07:37 EDT
*** Bug 1214308 has been marked as a duplicate of this bug. ***
Comment 9 Bryan Kearney 2015-08-11 09:18:10 EDT
This bug is slated to be released with Satellite 6.1.
Comment 10 errata-xmlrpc 2015-08-12 01:28:48 EDT
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

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