Bug 191146 - Activation Key Config Auto Deploy fails with "Illegal Function Call Attempted"
Summary: Activation Key Config Auto Deploy fails with "Illegal Function Call Attempted"
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Configuration Management
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Todd Sanders
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-09 06:32 UTC by Roel Gloudemans
Modified: 2009-08-22 03:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-22 03:03:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Roel Gloudemans 2006-05-09 06:32:29 UTC
Description of problem:

When bootstrapping the system we have a config channel included in one of the
activation keys. This results in 3 scheduled activities:
1) Activation Key Config File Deployment
2) Activation Key Package Auto-Install
3) Activation Key Config Auto-Deploy 

This last action structurally fails with "Illegal function call attempted". I
can find nothing in the log files about which function call it might be. But if
the action is rescheduled, it succeeds and the config files are deployed.

Version-Release number of selected component (if applicable):
Satellite 4.0.6 on RHAS3_U6. Client is RHAS3_U6

How reproducible:
Always

Steps to Reproduce:
1. Bootstrap
2.
3.
  
Actual results:
Config files are not deployed

Expected results:
Config files deployed

Comment 1 Roel Gloudemans 2006-06-21 05:51:28 UTC
This is solved in Update 7.

Comment 2 Kyle Gonzales 2006-08-03 16:21:54 UTC
I'm seeing this issue on a RHEL3U5 system, that has the most recent versions of
up2date, rpm, rhnlib, and all dependencies installed by the activation key.

I can, immediately after the activation is complete, run "rhncfg-client get" and
get the files.  I can also schedule the deployment of the configs in the GUI,
then run rhn_check on the system.  That works too.

It just does not work during the activation of the system.

This is in RHN410.

Comment 3 Red Hat Bugzilla 2007-04-12 00:40:30 UTC
User bnackash's account has been closed

Comment 4 Red Hat Bugzilla 2007-05-03 05:39:42 UTC
User wregglej's account has been closed

Comment 6 Clifford Perry 2009-08-22 03:03:35 UTC
seems to be fixed. Closing out. Please open a support ticket if further assistance is needed. 

Cliff


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