Bug 193764
Summary: | config channels not deployed during kickstart | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Kurt Keller <kurt> |
Component: | Provisioning | Assignee: | Mike McCune <mmccune> |
Status: | CLOSED WONTFIX | QA Contact: | Brandon Perkins <bperkins> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | cperry |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-08-22 03:06:58 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: |
User bnackash's account has been closed Satellite 3.x has EOL'd. Closing this bug out. http://www.redhat.com/security/updates/satellite/ Regards, Cliff |
Description of problem: Files from config channels are not deployed upon kickstart. Version-Release number of selected component (if applicable): satellite server 3.7.0 (training location) under RHEL-4-ES-U2 satellite server 3.6.x to be rechecked when back at the office, but I know one of my coworkers mentioned something about file not being deployed too How reproducible: always Steps to Reproduce: 1. create config channel 2. add files to config channel 3. setup config channel files to be deployed automatically when kickstarting 4. kickstart client Actual results: The kickstarted machine shows a failed event in the satellite with the following text: > This action's status is: Failed. > The client picked up this action on 2006-06-01 15:30:06 CEST. > The client completed this action on 2006-06-01 15:30:06 CEST. > Client execution returned "Invalid function call attempted" (code 6) and the config files are not deployed Expected results: The files should be deployed upon kickstarting. Additional info: - deploying the files later on manually works fine - possible workaround: add the following line to the post section of the kickstart file: rhncfg-client get