Changes in kickstart file do not take effect in Cobbler.

[Gi Dot]

I am using Cobbler to install SLES 11 SP2 and it has been running fine all
the while. Recently I modified the kickstart file by changing the size of
the root partition from 18GB to 36GB. To my surprise the modification did
not take place - Cobbler created a root partition with the size of 18GB. I
tried removing the profile, renaming it, but no success.

I am completely stump as to where Cobbler is getting the value 18GB from.
Is there some kind of cache that is keeping the old kickstart file
somewhere and I need to clear that up first?

The part where I did the modification:

<partition>
  <create config:type="boolean">true</create>
  <crypt_fs config:type="boolean">false</crypt_fs>
  <filesystem config:type="symbol">ext3</filesystem>
  <format config:type="boolean">true</format>
  <fstopt>acl,user_xattr</fstopt>
  <loop_fs config:type="boolean">false</loop_fs>
  <lv_name>lvroot</lv_name>
  <mount>/</mount>
  <mountby config:type="symbol">device</mountby>
  <partition_id config:type="integer">131</partition_id>
  <raid_options/>
  <resize config:type="boolean">false</resize>
  <size>36GB</size>
</partition>


Any help is appreciated.

Thanks.

[Jörgen Maas]

There's no caching, all autoinstall templates are generated on-the-fly.
Are you sure you've included the snippet into the autoyast.xml associated
with that system/profile?

On Wed, Apr 22, 2015 at 6:28 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:

>  I am using Cobbler to install SLES 11 SP2 and it has been running
> fine all
>  the while. Recently I modified the kickstart file by changing the size of
>  the root partition from 18GB to 36GB. To my surprise the modification did
>  not take place - Cobbler created a root partition with the size of 18GB. I
>  tried removing the profile, renaming it, but no success.
>
>  I am completely stump as to where Cobbler is getting the value 18GB from.
>  Is there some kind of cache that is keeping the old kickstart file
>  somewhere and I need to clear that up first?
>
>  The part where I did the modification:
>
>  <partition>
>    <create config:type="boolean">true</create>
>    <crypt_fs config:type="boolean">false</crypt_fs>
>    <filesystem config:type="symbol">ext3</filesystem>
>    <format config:type="boolean">true</format>
>    <fstopt>acl,user_xattr</fstopt>
>    <loop_fs config:type="boolean">false</loop_fs>
>    <lv_name>lvroot</lv_name>
>    <mount>/</mount>
>    <mountby config:type="symbol">device</mountby>
>    <partition_id config:type="integer">131</partition_id>
>    <raid_options/>
>    <resize config:type="boolean">false</resize>
>    <size>36GB</size>
>  </partition>
>
>
>  Any help is appreciated.
>
>  Thanks.
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>  

-- 
Grtz,
Jörgen Maas

[Gi Dot]

Yea, that's what I thought. My kickstart file is accessed via http, and it
is definitely accessible. Anyway I did try copying the kickstart file into
/var/lib/cobbler/kickstarts, and run cobbler system getks --name=test, and
all was good. It's the right kickstart file, the right profile, the right
values. Thanks.

On Wed, Apr 22, 2015 at 12:41 PM, Jörgen Maas <jorgen.maas(a)gmail.com&gt; wrote:

>  There's no caching, all autoinstall templates are generated
> on-the-fly.
>  Are you sure you've included the snippet into the autoyast.xml associated
>  with that system/profile?
>
>  On Wed, Apr 22, 2015 at 6:28 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:
>
> > I am using Cobbler to install SLES 11 SP2 and it has been running fine
> > all the while. Recently I modified the kickstart file by changing the size
> > of the root partition from 18GB to 36GB. To my surprise the modification
> > did not take place - Cobbler created a root partition with the size of
> > 18GB. I tried removing the profile, renaming it, but no success.
> >
> > I am completely stump as to where Cobbler is getting the value 18GB from.
> > Is there some kind of cache that is keeping the old kickstart file
> > somewhere and I need to clear that up first?
> >
> > The part where I did the modification:
> >
> > <partition>
> >   <create config:type="boolean">true</create>
> >   <crypt_fs config:type="boolean">false</crypt_fs>
> >   <filesystem config:type="symbol">ext3</filesystem>
> >   <format config:type="boolean">true</format>
> >   <fstopt>acl,user_xattr</fstopt>
> >   <loop_fs config:type="boolean">false</loop_fs>
> >   <lv_name>lvroot</lv_name>
> >   <mount>/</mount>
> >   <mountby config:type="symbol">device</mountby>
> >   <partition_id config:type="integer">131</partition_id>
> >   <raid_options/>
> >   <resize config:type="boolean">false</resize>
> >   <size>36GB</size>
> > </partition>
> >
> >
> > Any help is appreciated.
> >
> > Thanks.
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://lists.fedorahosted.org/mailman/listinfo/cobbler
> >
> >
>
>
>  --
>  Grtz,
>  Jörgen Maas
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>

[Marold, Drew]

Are you reinstalling over an existing system, or a totally new one ? If the former,  does
your kickstart include the stanza to remove any existing partitions ?

# Partition clearing information
clearpart --all

From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:[e-mail]] On Behalf Of Gi Dot
Sent: Wednesday, April 22, 2015 00:29
To: cobbler(a)lists.fedorahosted.org
Subject: [cobbler] Changes in kickstart file do not take effect in Cobbler.

I am using Cobbler to install SLES 11 SP2 and it has been running fine all the while.
Recently I modified the kickstart file by changing the size of the root partition from
18GB to 36GB. To my surprise the modification did not take place - Cobbler created a root
partition with the size of 18GB. I tried removing the profile, renaming it, but no
success.

I am completely stump as to where Cobbler is getting the value 18GB from. Is there some
kind of cache that is keeping the old kickstart file somewhere and I need to clear that up
first?

The part where I did the modification:

<partition>
  <create config:type="boolean">true</create>
  <crypt_fs config:type="boolean">false</crypt_fs>
  <filesystem config:type="symbol">ext3</filesystem>
  <format config:type="boolean">true</format>
  <fstopt>acl,user_xattr</fstopt>
  <loop_fs config:type="boolean">false</loop_fs>
  <lv_name>lvroot</lv_name>
  <mount>/</mount>
  <mountby config:type="symbol">device</mountby>
  <partition_id config:type="integer">131</partition_id>
  <raid_options/>
  <resize config:type="boolean">false</resize>
  <size>36GB</size>
</partition>


Any help is appreciated.

Thanks.

[Gi Dot]

It is a reinstall over an existing system, though I'm pretty sure I did try
on a new system as well. The 'clearpart -all' is how you clear partitions
with CentOS kickstart? In my SuSE autoyast kickstart file I have this:

<initialize config:type="boolean">true</initialize>
## If set to "true", the partition table gets wiped out before AutoYaST
starts the partition calculation.

During the installation I can see that all of the partitions got wiped out,
but during the creation, the old values took place.


On Wed, Apr 22, 2015 at 9:17 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
wrote:

>   Are you reinstalling over an existing system, or a totally new one ?
> If
>  the former,  does your kickstart include the stanza to remove any existing
>  partitions ?
>
>
>
>  # Partition clearing information
>
>  clearpart --all
>
>
>
>  *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
>  cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
>  *Sent:* Wednesday, April 22, 2015 00:29
>  *To:* cobbler(a)lists.fedorahosted.org
>  *Subject:* [cobbler] Changes in kickstart file do not take effect in
>  Cobbler.
>
>
>
>  I am using Cobbler to install SLES 11 SP2 and it has been running fine all
>  the while. Recently I modified the kickstart file by changing the size of
>  the root partition from 18GB to 36GB. To my surprise the modification did
>  not take place - Cobbler created a root partition with the size of 18GB. I
>  tried removing the profile, renaming it, but no success.
>
>  I am completely stump as to where Cobbler is getting the value 18GB from.
>  Is there some kind of cache that is keeping the old kickstart file
>  somewhere and I need to clear that up first?
>
>  The part where I did the modification:
>
>  <partition>
>    <create config:type="boolean">true</create>
>    <crypt_fs config:type="boolean">false</crypt_fs>
>    <filesystem config:type="symbol">ext3</filesystem>
>    <format config:type="boolean">true</format>
>    <fstopt>acl,user_xattr</fstopt>
>    <loop_fs config:type="boolean">false</loop_fs>
>    <lv_name>lvroot</lv_name>
>    <mount>/</mount>
>    <mountby config:type="symbol">device</mountby>
>    <partition_id config:type="integer">131</partition_id>
>    <raid_options/>
>    <resize config:type="boolean">false</resize>
>    <size>36GB</size>
>  </partition>
>
>
>  Any help is appreciated.
>
>  Thanks.
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>

[Gi Dot]

Update: I tried on a brand new server, and still the same. I am baffled.

On Thu, Apr 23, 2015 at 10:14 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:

>  It is a reinstall over an existing system, though I'm pretty sure
> I did
>  try on a new system as well. The 'clearpart -all' is how you clear
>  partitions with CentOS kickstart? In my SuSE autoyast kickstart file I have
>  this:
>
>  <initialize config:type="boolean">true</initialize>
>  ## If set to "true", the partition table gets wiped out before AutoYaST
>  starts the partition calculation.
>
>  During the installation I can see that all of the partitions got wiped
>  out, but during the creation, the old values took place.
>
>
>  On Wed, Apr 22, 2015 at 9:17 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
>  wrote:
>
> >  Are you reinstalling over an existing system, or a totally new one ? If
> > the former,  does your kickstart include the stanza to remove any existing
> > partitions ?
> >
> >
> >
> > # Partition clearing information
> >
> > clearpart --all
> >
> >
> >
> > *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
> > cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
> > *Sent:* Wednesday, April 22, 2015 00:29
> > *To:* cobbler(a)lists.fedorahosted.org
> > *Subject:* [cobbler] Changes in kickstart file do not take effect in
> > Cobbler.
> >
> >
> >
> > I am using Cobbler to install SLES 11 SP2 and it has been running fine
> > all the while. Recently I modified the kickstart file by changing the size
> > of the root partition from 18GB to 36GB. To my surprise the modification
> > did not take place - Cobbler created a root partition with the size of
> > 18GB. I tried removing the profile, renaming it, but no success.
> >
> > I am completely stump as to where Cobbler is getting the value 18GB from.
> > Is there some kind of cache that is keeping the old kickstart file
> > somewhere and I need to clear that up first?
> >
> > The part where I did the modification:
> >
> > <partition>
> >   <create config:type="boolean">true</create>
> >   <crypt_fs config:type="boolean">false</crypt_fs>
> >   <filesystem config:type="symbol">ext3</filesystem>
> >   <format config:type="boolean">true</format>
> >   <fstopt>acl,user_xattr</fstopt>
> >   <loop_fs config:type="boolean">false</loop_fs>
> >   <lv_name>lvroot</lv_name>
> >   <mount>/</mount>
> >   <mountby config:type="symbol">device</mountby>
> >   <partition_id config:type="integer">131</partition_id>
> >   <raid_options/>
> >   <resize config:type="boolean">false</resize>
> >   <size>36GB</size>
> > </partition>
> >
> >
> > Any help is appreciated.
> >
> > Thanks.
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://lists.fedorahosted.org/mailman/listinfo/cobbler
> >
> >
>

[Gi Dot]

My kickstart file for reference.

http://pastebin.com/HxfUkFE8

On Thu, Apr 23, 2015 at 3:56 PM, Gi Dot <gadidot(a)gmail.com&gt; wrote:

>  Update: I tried on a brand new server, and still the same. I am
> baffled.
>
>  On Thu, Apr 23, 2015 at 10:14 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:
>
> > It is a reinstall over an existing system, though I'm pretty sure I did
> > try on a new system as well. The 'clearpart -all' is how you clear
> > partitions with CentOS kickstart? In my SuSE autoyast kickstart file I have
> > this:
> >
> > <initialize config:type="boolean">true</initialize>
> > ## If set to "true", the partition table gets wiped out before AutoYaST
> > starts the partition calculation.
> >
> > During the installation I can see that all of the partitions got wiped
> > out, but during the creation, the old values took place.
> >
> >
> > On Wed, Apr 22, 2015 at 9:17 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
> > wrote:
> >
> >>  Are you reinstalling over an existing system, or a totally new one ?
> >> If the former,  does your kickstart include the stanza to remove any
> >> existing partitions ?
> >>
> >>
> >>
> >> # Partition clearing information
> >>
> >> clearpart --all
> >>
> >>
> >>
> >> *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
> >> cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
> >> *Sent:* Wednesday, April 22, 2015 00:29
> >> *To:* cobbler(a)lists.fedorahosted.org
> >> *Subject:* [cobbler] Changes in kickstart file do not take effect in
> >> Cobbler.
> >>
> >>
> >>
> >> I am using Cobbler to install SLES 11 SP2 and it has been running fine
> >> all the while. Recently I modified the kickstart file by changing the size
> >> of the root partition from 18GB to 36GB. To my surprise the modification
> >> did not take place - Cobbler created a root partition with the size of
> >> 18GB. I tried removing the profile, renaming it, but no success.
> >>
> >> I am completely stump as to where Cobbler is getting the value 18GB
> >> from. Is there some kind of cache that is keeping the old kickstart file
> >> somewhere and I need to clear that up first?
> >>
> >> The part where I did the modification:
> >>
> >> <partition>
> >>   <create config:type="boolean">true</create>
> >>   <crypt_fs config:type="boolean">false</crypt_fs>
> >>   <filesystem config:type="symbol">ext3</filesystem>
> >>   <format config:type="boolean">true</format>
> >>   <fstopt>acl,user_xattr</fstopt>
> >>   <loop_fs config:type="boolean">false</loop_fs>
> >>   <lv_name>lvroot</lv_name>
> >>   <mount>/</mount>
> >>   <mountby config:type="symbol">device</mountby>
> >>   <partition_id config:type="integer">131</partition_id>
> >>   <raid_options/>
> >>   <resize config:type="boolean">false</resize>
> >>   <size>36GB</size>
> >> </partition>
> >>
> >>
> >> Any help is appreciated.
> >>
> >> Thanks.
> >>
> >> _______________________________________________
> >> cobbler mailing list
> >> cobbler(a)lists.fedorahosted.org
> >> https://lists.fedorahosted.org/mailman/listinfo/cobbler
> >>
> >>
> >
>

[Marold, Drew]

Is the /opt volume getting created as 36GB or is it also getting 18 ? Does changing the
size value on that one work ? How big is the drive overall ?

From: cobbler-bounces(a)lists.fedorahosted.org
[mailto:[e-mail]] On Behalf Of Gi Dot
Sent: Thursday, April 23, 2015 05:51
To: cobbler mailing list
Subject: Re: [cobbler] Changes in kickstart file do not take effect in Cobbler.

My kickstart file for reference.

http://pastebin.com/HxfUkFE8

On Thu, Apr 23, 2015 at 3:56 PM, Gi Dot
<[e-mail]<mailto:[e-mail]>> wrote:
Update: I tried on a brand new server, and still the same. I am baffled.

On Thu, Apr 23, 2015 at 10:14 AM, Gi Dot
<[e-mail]<mailto:[e-mail]>> wrote:
It is a reinstall over an existing system, though I'm pretty sure I did try on a new
system as well. The 'clearpart -all' is how you clear partitions with CentOS
kickstart? In my SuSE autoyast kickstart file I have this:

<initialize config:type="boolean">true</initialize>
## If set to "true", the partition table gets wiped out before AutoYaST starts
the partition calculation.
During the installation I can see that all of the partitions got wiped out, but during the
creation, the old values took place.

On Wed, Apr 22, 2015 at 9:17 PM, Marold, Drew
<[e-mail]<mailto:[e-mail]>> wrote:
Are you reinstalling over an existing system, or a totally new one ? If the former,  does
your kickstart include the stanza to remove any existing partitions ?

# Partition clearing information
clearpart --all

From:
[e-mail]<mailto:[e-mail]>
[mailto:[e-mail]<mailto:[e-mail]>]
On Behalf Of Gi Dot
Sent: Wednesday, April 22, 2015 00:29
To: [e-mail]<mailto:[e-mail]>
Subject: [cobbler] Changes in kickstart file do not take effect in Cobbler.

I am using Cobbler to install SLES 11 SP2 and it has been running fine all the while.
Recently I modified the kickstart file by changing the size of the root partition from
18GB to 36GB. To my surprise the modification did not take place - Cobbler created a root
partition with the size of 18GB. I tried removing the profile, renaming it, but no
success.

I am completely stump as to where Cobbler is getting the value 18GB from. Is there some
kind of cache that is keeping the old kickstart file somewhere and I need to clear that up
first?

The part where I did the modification:

<partition>
  <create config:type="boolean">true</create>
  <crypt_fs config:type="boolean">false</crypt_fs>
  <filesystem config:type="symbol">ext3</filesystem>
  <format config:type="boolean">true</format>
  <fstopt>acl,user_xattr</fstopt>
  <loop_fs config:type="boolean">false</loop_fs>
  <lv_name>lvroot</lv_name>
  <mount>/</mount>
  <mountby config:type="symbol">device</mountby>
  <partition_id config:type="integer">131</partition_id>
  <raid_options/>
  <resize config:type="boolean">false</resize>
  <size>36GB</size>
</partition>


Any help is appreciated.

Thanks.

_______________________________________________
cobbler mailing list
[e-mail]<mailto:[e-mail]>
https://lists.fedorahosted.org/mailman/listinfo/cobbler

[Gi Dot]

@Alan, Yes you're absolutely right. My mistake to refer it as a kickstart.
I have always assumed 'kickstart' as a generic term for all auto
installation files, like autoyast. Learned my lesson when I first played
with spacewalk and I was wondering why the kickstart file option was greyed
out for SuSe distro :P. Thanks.

@Drew, Originally the value for /opt is 30GB. I modified it to 36GB, to see
if it changes. No go. The setup is 2 drives, each with the size of 300GB,
configured as RAID1 (hardware RAID). Now come to think about it, not long
ago I added a post-script in the autoyast file, but it never got executed.
The changes must have not been picked up at all. So I guess it's not just a
partition problem. Any changes just won't take effect. I'll do more testing
when I have the chance. Thanks.

On Thu, Apr 23, 2015 at 9:26 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
wrote:

>   Is the /opt volume getting created as 36GB or is it also getting 18
> ?
>  Does changing the size value on that one work ? How big is the drive
>  overall ?
>
>
>
>  *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
>  cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
>  *Sent:* Thursday, April 23, 2015 05:51
>  *To:* cobbler mailing list
>  *Subject:* Re: [cobbler] Changes in kickstart file do not take effect in
>  Cobbler.
>
>
>
>  My kickstart file for reference.
>
>  http://pastebin.com/HxfUkFE8
>
>
>
>  On Thu, Apr 23, 2015 at 3:56 PM, Gi Dot <gadidot(a)gmail.com&gt; wrote:
>
>  Update: I tried on a brand new server, and still the same. I am baffled.
>
>
>
>  On Thu, Apr 23, 2015 at 10:14 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:
>
>  It is a reinstall over an existing system, though I'm pretty sure I did
>  try on a new system as well. The 'clearpart -all' is how you clear
>  partitions with CentOS kickstart? In my SuSE autoyast kickstart file I have
>  this:
>
>  <initialize config:type="boolean">true</initialize>
>  ## If set to "true", the partition table gets wiped out before AutoYaST
>  starts the partition calculation.
>
>  During the installation I can see that all of the partitions got wiped
>  out, but during the creation, the old values took place.
>
>
>
>  On Wed, Apr 22, 2015 at 9:17 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
>  wrote:
>
>    Are you reinstalling over an existing system, or a totally new one ? If
>  the former,  does your kickstart include the stanza to remove any existing
>  partitions ?
>
>
>
>  # Partition clearing information
>
>  clearpart --all
>
>
>
>  *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
>  cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
>  *Sent:* Wednesday, April 22, 2015 00:29
>  *To:* cobbler(a)lists.fedorahosted.org
>  *Subject:* [cobbler] Changes in kickstart file do not take effect in
>  Cobbler.
>
>
>
>  I am using Cobbler to install SLES 11 SP2 and it has been running fine all
>  the while. Recently I modified the kickstart file by changing the size of
>  the root partition from 18GB to 36GB. To my surprise the modification did
>  not take place - Cobbler created a root partition with the size of 18GB. I
>  tried removing the profile, renaming it, but no success.
>
>  I am completely stump as to where Cobbler is getting the value 18GB from.
>  Is there some kind of cache that is keeping the old kickstart file
>  somewhere and I need to clear that up first?
>
>  The part where I did the modification:
>
>  <partition>
>    <create config:type="boolean">true</create>
>    <crypt_fs config:type="boolean">false</crypt_fs>
>    <filesystem config:type="symbol">ext3</filesystem>
>    <format config:type="boolean">true</format>
>    <fstopt>acl,user_xattr</fstopt>
>    <loop_fs config:type="boolean">false</loop_fs>
>    <lv_name>lvroot</lv_name>
>    <mount>/</mount>
>    <mountby config:type="symbol">device</mountby>
>    <partition_id config:type="integer">131</partition_id>
>    <raid_options/>
>    <resize config:type="boolean">false</resize>
>    <size>36GB</size>
>  </partition>
>
>
>  Any help is appreciated.
>
>  Thanks.
>
>
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>
>
>
>
>
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>

[Gi Dot]

Hi,

I finally figured out where Cobbler picked up the value from. In my
/var/lib/tftpboot/uefi/elilo.conf, I have the following:

prompt
timeout=100
default=linux

image=linux
       label=linux
       description = "Installation"
       initrd=initrd
       append="/images/slestest/initrd textmode=1 install=
http://192.168.0.10/sles/mnt autoyast=
http://192.168.0.10/sles/autoyast/old.xml"


I tried to remove the autoyast part where it points to the old autoyast
file, but then Cobbler won't start the installation automatically. It seems
like the profile that I added into Cobbler using "cobbler profile add" is
pretty much pointless. How do I fix this?

Thanks.

On Fri, Apr 24, 2015 at 3:06 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:

>  @Alan, Yes you're absolutely right. My mistake to refer it as a
> kickstart.
>  I have always assumed 'kickstart' as a generic term for all auto
>  installation files, like autoyast. Learned my lesson when I first played
>  with spacewalk and I was wondering why the kickstart file option was greyed
>  out for SuSe distro :P. Thanks.
>
>  @Drew, Originally the value for /opt is 30GB. I modified it to 36GB, to
>  see if it changes. No go. The setup is 2 drives, each with the size of
>  300GB, configured as RAID1 (hardware RAID). Now come to think about it, not
>  long ago I added a post-script in the autoyast file, but it never got
>  executed. The changes must have not been picked up at all. So I guess it's
>  not just a partition problem. Any changes just won't take effect. I'll do
>  more testing when I have the chance. Thanks.
>
>  On Thu, Apr 23, 2015 at 9:26 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
>  wrote:
>
> >  Is the /opt volume getting created as 36GB or is it also getting 18 ?
> > Does changing the size value on that one work ? How big is the drive
> > overall ?
> >
> >
> >
> > *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
> > cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
> > *Sent:* Thursday, April 23, 2015 05:51
> > *To:* cobbler mailing list
> > *Subject:* Re: [cobbler] Changes in kickstart file do not take effect in
> > Cobbler.
> >
> >
> >
> > My kickstart file for reference.
> >
> > http://pastebin.com/HxfUkFE8
> >
> >
> >
> > On Thu, Apr 23, 2015 at 3:56 PM, Gi Dot <gadidot(a)gmail.com&gt; wrote:
> >
> > Update: I tried on a brand new server, and still the same. I am baffled.
> >
> >
> >
> > On Thu, Apr 23, 2015 at 10:14 AM, Gi Dot <gadidot(a)gmail.com&gt; wrote:
> >
> > It is a reinstall over an existing system, though I'm pretty sure I did
> > try on a new system as well. The 'clearpart -all' is how you clear
> > partitions with CentOS kickstart? In my SuSE autoyast kickstart file I have
> > this:
> >
> > <initialize config:type="boolean">true</initialize>
> > ## If set to "true", the partition table gets wiped out before AutoYaST
> > starts the partition calculation.
> >
> > During the installation I can see that all of the partitions got wiped
> > out, but during the creation, the old values took place.
> >
> >
> >
> > On Wed, Apr 22, 2015 at 9:17 PM, Marold, Drew <drew.marold(a)bluecoat.com&gt;
> > wrote:
> >
> >   Are you reinstalling over an existing system, or a totally new one ?
> > If the former,  does your kickstart include the stanza to remove any
> > existing partitions ?
> >
> >
> >
> > # Partition clearing information
> >
> > clearpart --all
> >
> >
> >
> > *From:* cobbler-bounces(a)lists.fedorahosted.org [mailto:
> > cobbler-bounces(a)lists.fedorahosted.org] *On Behalf Of *Gi Dot
> > *Sent:* Wednesday, April 22, 2015 00:29
> > *To:* cobbler(a)lists.fedorahosted.org
> > *Subject:* [cobbler] Changes in kickstart file do not take effect in
> > Cobbler.
> >
> >
> >
> > I am using Cobbler to install SLES 11 SP2 and it has been running fine
> > all the while. Recently I modified the kickstart file by changing the size
> > of the root partition from 18GB to 36GB. To my surprise the modification
> > did not take place - Cobbler created a root partition with the size of
> > 18GB. I tried removing the profile, renaming it, but no success.
> >
> > I am completely stump as to where Cobbler is getting the value 18GB from.
> > Is there some kind of cache that is keeping the old kickstart file
> > somewhere and I need to clear that up first?
> >
> > The part where I did the modification:
> >
> > <partition>
> >   <create config:type="boolean">true</create>
> >   <crypt_fs config:type="boolean">false</crypt_fs>
> >   <filesystem config:type="symbol">ext3</filesystem>
> >   <format config:type="boolean">true</format>
> >   <fstopt>acl,user_xattr</fstopt>
> >   <loop_fs config:type="boolean">false</loop_fs>
> >   <lv_name>lvroot</lv_name>
> >   <mount>/</mount>
> >   <mountby config:type="symbol">device</mountby>
> >   <partition_id config:type="integer">131</partition_id>
> >   <raid_options/>
> >   <resize config:type="boolean">false</resize>
> >   <size>36GB</size>
> > </partition>
> >
> >
> > Any help is appreciated.
> >
> > Thanks.
> >
> >
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://lists.fedorahosted.org/mailman/listinfo/cobbler
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://lists.fedorahosted.org/mailman/listinfo/cobbler
> >
> >
>

[Alan Evangelista]

On 04/22/2015 11:14 PM, Gi Dot wrote:
>  It is a reinstall over an existing system, though I'm pretty sure
> I 
>  did try on a new system as well. The 'clearpart -all' is how you clear 
>  partitions with CentOS kickstart? In my SuSE autoyast kickstart file I 
>  have this: 
Side-comments:
1) clearpart is a kickstart directive, it works equally in any Red Hat 
based distribution which accepts kickstarts, not only CentOS
2) there is no "autoyast kickstart file". Red Hat based distributions 
use kickstart, Suse based distributions use autoyast. Probably you meant 
"autoyast file"


Regards,
Alan Evangelista