[Spacewalk-list] CentOS 6 Related Kickstart Problem in Spacewalk

[Jonathan Scott]

I do just that, Giovanni; build with just the base channel, spacewalk
client channel, and a custom collection channel, Then attach the updates
channel via activation key, and finish up with a yum update as the last
item in the final %post script. Works like a charm.

- Jonathan

On Tue, Feb 12, 2013 at 3:18 PM, Giovanni Torres <giovtorres at hotmail.com>wrote:

> Is there not a libxml2-python in the Base channel?  As far as I know, if
> you include the Updates repo in the kickstart on CentOS 6, the kickstart
> process will fail.  (See here: http://bugs.centos.org/view.php?id=4978)
>
> I use the activation key to include the Updates repo on the system *after*
> the kickstart is completed.  Then I run the yum update manually after.  I'm
> not sure whether its ok to do 'yum update' at the tail end of the %post in
> a kickstart.
>
> Giovanni
>
> > From: trevor.t.kates at dom.com
> > To: spacewalk-list at redhat.com
> > Date: Tue, 12 Feb 2013 14:55:45 -0500
> > Subject: [Spacewalk-list] CentOS 6 Related Kickstart Problem in Spacewalk
> >
> > Hi,
> >
> > My attempts to solve this problem solo have been met with much
> frustration. I am attempting to kickstart a CentOS 6.3 system via pxeboot,
> cobbler and Spacewalk. I have an activation key set up to load several
> configuration files upon registration which is also supposed to install
> relevant rhn packages. An error occurs when attempting to install
> libxml2-python because the version of this package that the kickstart is
> attempting to install originates from the CentOS 6 updates repo channel;
> however, the dependency for this package which is also in the CentOS 6
> updates repo channel is unavailable because the repo is not enabled in the
> kickstart. If I enable the repo in the kickstart, the install will not
> complete and produces an install.log file full of errors like the following:
> >
> > Installing postfix-2.6.6-2.2.el6_1.x86_64
> > warning: %post(postfix-2.6.6-2.2.el6_1.x86_64) scriptlet failed, exit
> status 127
> >
> > I’m at a loss at the moment for how to properly fix this problem as all
> of my searches have turned up no viable solutions. Any help here would be
> appreciated.
> >
> > Thanks,
> >
> >
> _______________________________________________________________________________
> > Trevor T. Kates
> >
> >
> > CONFIDENTIALITY NOTICE: This electronic message contains
> > information which may be legally confidential and/or privileged and
> > does not in any case represent a firm ENERGY COMMODITY bid or offer
> > relating thereto which binds the sender without an additional
> > express written confirmation to that effect. The information is
> > intended solely for the individual or entity named above and access
> > by anyone else is unauthorized. If you are not the intended
> > recipient, any disclosure, copying, distribution, or use of the
> > contents of this information is prohibited and may be unlawful. If
> > you have received this electronic transmission in error, please
> > reply immediately to the sender that you have received the message
> > in error, and delete it. Thank you.
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130212/0148ac0d/attachment.htm>