I'm not making any accusations here - I'm only asking if this was decided to be the new behaviour for Spacewalk/Satellite/Cobbler. Should there be an inconsistency between fresh kickstart installs and re-provisions?
It is intended that, if you have the network configuration snippets referenced in your kickstart templates, that you will be using the network configuration scripts that Cobbler generates rather than pushing out your own. If you don't have those snippets there, things just work.
If existing Spacewalk generated (templated, not raw uploaded) scripts insert these snippets blindly into existing kickstarts, that might be a bug in Satellite, as they should generate the same kickstart output (essentially) both before and after the upgrade -- I agree with that. I don't agree that Cobbler broke it... Spacewalk's particular usage of Cobbler, yes.
If you are using self-uploaded-into-Spacewalk kickstart templates based on /var/lib/cobbler/kickstarts/sample*.ks, then you would need to remove the network configuration portions if you wanted to write your own things in %post.
I can mostly speak for Cobbler and not Spacewalk, so perhaps Spacewalk folks can weigh in with what you'd need to do.
Thanks Duncan Innes _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
_______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
