Project

General

Profile

Actions

Bug #15192

closed

subscription-manager using activation key is failing in katello 3.0 RC5

Added by Dylan Baars almost 8 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hi,

having got the boot disk based imaging working again (yay for reboots!! See bug# 15128) I imaged a machine successfully but it is having problems with subscription-manager

On the machine:
From the imaging process logs, I saw this:

Installed:
subscription-manager.x86_64 0:1.15.9-15.el7.centos.0.1

Dependency Installed:
libnl.x86_64 0:1.1.4-3.el7 m2crypto.x86_64 0:0.21.1-17.el7
python-dmidecode.x86_64 0:3.10.13-11.el7 python-ethtool.x86_64 0:0.8-5.el7
python-rhsm.x86_64 0:1.15.4-5.el7 usermode.x86_64 0:1.111-5.el7

Complete!
Retrieving http://wellkatellodev.niwa.local/pub/katello-ca-consumer-latest.noarch.rpm
Preparing... ########################################
Updating / installing...
katello-ca-consumer-wellkatellodev.niw########################################
Registering the System
undefined method `[]' for nil:NilClass
The system has been registered with ID: 7808f40d-42e1-4691-8bf5-6b761d17b2ae
Installing Katello Agent

Although the machine registered, it did not receive any repositories - i.e. /etc/yum.repos.d/redhat.repo did not exist

Given the kickstart failed, I tried re-registering with a different activation key

[root@testcislave01d ~]# subscription-manager register --org="NIWA" --activationkey="Standard Production Server" --force
The system with UUID 082bf247-b597-4d4e-9797-b1211a67ef4d has been unregistered
The system has been registered with ID: 4f81acfe-0acb-4d38-8eda-305a75d86f38
undefined method `[]' for nil:NilClass
[root@testcislave01d ~]#

production.log is attached.


Files

rhsm.log rhsm.log 84.4 KB Dylan Baars, 05/25/2016 09:53 PM
production.log production.log 78.3 KB Dylan Baars, 05/26/2016 08:04 PM
Actions #1

Updated by Eric Helms almost 8 years ago

  • Status changed from New to Need more information

Do you have the traceback for

undefined method `[]' for nil:NilClass
?

Actions #2

Updated by Dylan Baars almost 8 years ago

Eric Helms wrote:

Do you have the traceback for [...] ?

Attached /var/log/rhsm/rhsm.log from the VM

Actions #3

Updated by Eric Helms almost 8 years ago

The traceback would need to come from the production.log on the server -- sorry for not clarifying that.

Actions #4

Updated by Dylan Baars almost 8 years ago

Eric Helms wrote:

The traceback would need to come from the production.log on the server -- sorry for not clarifying that.

Oh sorry! For some reason I thought I had attached that :-/ Here it is :-)

Actions #5

Updated by Eric Helms almost 8 years ago

Can you give us some info on what all fields you have configured on your activation key? The specific items aren't important but things like types of subscriptions added, release set or not, service level set or not, product content edited etc.

Actions #6

Updated by Dylan Baars almost 8 years ago

Eric Helms wrote:

Can you give us some info on what all fields you have configured on your activation key? The specific items aren't important but things like types of subscriptions added, release set or not, service level set or not, product content edited etc.

Yep no worries - if a field isn't set or doesn't have any data I've added "Not Set" below...
From the Details tab:
Name: Standard Production Server
Description: Not set
Host limit: Unlimited
Service Level: Not set

Release version: Not set
Environment: Prod-Server
Content view: CentOS7-Server

Subscriptions tab
Auto-attach: Yes
4 products attached, CentOS7, EPEL7, Katello Agent, Saltstack - all YUM repositories

Product content tab
Not touched, all at default

is that what you're after?

Actions #7

Updated by george lim almost 8 years ago

yup i'm seeing the same issue as well. I noticed that redhat.repo file doesn't get created.

Actions #8

Updated by Justin Sherrill almost 8 years ago

The commit from https://github.com/Katello/katello/pull/6004 (http://projects.theforeman.org/issues/14824) fixed an issue introduced by Rails 4.2. Since 3.0 is still on Rails 4.1 we need to revert this fix from the 3.0 branch.

Actions #9

Updated by The Foreman Bot almost 8 years ago

  • Status changed from Need more information to Ready For Testing
  • Assignee set to Justin Sherrill
  • Pull request https://github.com/Katello/katello/pull/6096 added
Actions #10

Updated by Dylan Baars almost 8 years ago

Justin Sherrill wrote:

The commit from https://github.com/Katello/katello/pull/6004 (http://projects.theforeman.org/issues/14824) fixed an issue introduced by Rails 4.2. Since 3.0 is still on Rails 4.1 we need to revert this fix from the 3.0 branch.

The change in https://github.com/Katello/katello/pull/6096 successfully fixed the issue on my dev box, thanks!

Dylan

Actions #11

Updated by Eric Helms almost 8 years ago

  • Status changed from Ready For Testing to Resolved
Actions

Also available in: Atom PDF