Bug 530177

So a couple of workarounds: 

A) use a raw-style kickstart.  (Create one on the kickstart upload page).
   This can be created from scratch or you can copy and paste an existing template for a kickstart (found in /var/lib/rhn/kickstarts/wizard).  


B) Change the post_install_network_config snippet in /var/lib/cobbler/snippets.

-Jusitn

Event posted on 27-10-2009 11:32am GMT by jwrigley

Sadly, our tools meant I overlooked this I-T so I thought I was starting
from scratch with escalating and I talked to mmccune last friday about
this.

I have a reproducer:

Satellite: dhcp-196.gsslab.fab.redhat.com (shell is root/redhat, WebUI is
satadmin/redhat)
Client: dhcp-1-226.fab.redhat.com (also root/redhat)

The kickstart profile in question is jwrigley-test-network-snippet.

We have shown that this only affects reprovisioning.

The reproducer runs like this:

1) Provision the machine with the kickstart profile by booting from CD or
the cobbler bootiso. You'll see on the client that the cobbler.ks has an
empty:
# Start post_install_network_config generated code
# End post_install_network_config generated code

and /etc/sysconfig/network-scripts/ifcfg-bond0 exists.

2) Reprovision from the web interface. This time, all the stuff from
/var/lib/cobbler/snippets/post_install_network_config is included in
/root/cobbler.ks

We pinned this down to the following in the post_install_network_config
script:

#if $getVar("system_name","") != "" ## this is being provisioned by
system records, not profile records

So a bare metal provision uses a cobber profile record, and a reprovision
uses a cobbler system record. The question is, since the satellite
doesn't expose the options that this snippet is supposed to enable (to my
understanding), and the script is effectively not used if using a profile
record, is there any use in having this script at all?

My recommendation to my customer for now is going to be to simply empty
that file, how we manage that with errata releases I'm not sure.


This event sent from IssueTracker by jwrigley 
 issue 355045

Here's an idea I would propose.  We move the snippet to be before customer provided %post sections so that the customer can make changes within their %post section and the changes won't be overwritten.

would that be ok for the customer?

Spoke to jwrigly and he liked the idea 

Fixed in spacewalk master:  dcc9a0f707631d16982f5df8e0e92c9d5ec03fd7

# VERIFIED

Applied a check against Satellites installed on RHEL4 and RHEL5 servers. The
packages of brew build fixed the issue:
spacewalk-java-0.5.44-66.el[4,5]sat
spacewalk-backend-0.5.28-40.el[4,5]sat

Scenario for verification was: apply a %post script that echo-s some comment in the /etc/sysconfig/network-scripts/ifcfg-eth0

Kickstart of the client system actually does applies the comment and not overwrites with the default values.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0105.html