Fresh Red Hat 6.4 kickstarts out-of-date

Question

I am using an updated rhel-x86_64-server-6.4 channel to kickstart RHEL 6.4. What can explain servers being kickstarted with an out-of-date RHEL?

I would like to kickstart the server with the latest packages. It uses the same channel for kickstarting as for updating.

After kickstarting I can type yum update -y, but I would like the systems to be kickstarted up-to-date.

score 2 · Answer 1 · answered Feb 02 '14 at 15:10

2

The short answer is: you can't use the kickstart to immediately be up-to-date, you need to include a yum update as port of the post-install.

The kickstart tree is to be accessible for systems that are yet to be deployed and have not been registered yet, in other words it is publicly accessible, where from the commercial point of view the up-to-date channels and updates should only be available for registered systems with valid subscriptions.

answered Feb 02 '14 at 15:10

HBruijn

72,524
21
127
192

You also have to register the system in `%post` before you can update it. – Michael Hampton Feb 02 '14 at 16:35

score 0 · Answer 2 · answered Feb 04 '14 at 00:28

0

The correct answer to the question is to run yum update -y as a post install script. This is done in the %post section of your kickstart file. This will ensure the system comes up fully patched.

answered Feb 04 '14 at 00:28

Gestellen

35
1
7

Fresh Red Hat 6.4 kickstarts out-of-date

2 Answers2