Hi all katello/foreman experts,
I have a ptable template written as follows:
<%#
kind: ptable
name: odw_centos_workstation
oses:
- CentOS 5
- CentOS 6
- CentOS 7
%>
zerombr
clearpart --all --initlabel
part /boot --fstype=ext4 --size=500
part pv.1 --grow --size=1
volgroup vg_system --pesize=4096 pv.1
logvol / --fstype=ext4 --name=lv_root --vgname=vg_system --size=1024
–maxsize=51200
logvol swap --name=lv_swap --vgname=vg_system --size=8000 --maxsize=8000
logvol /srv/scratch --fstype=ext4 --name=lv_tmp --vgname=vg_system --grow
–size=1024
but when the system was kickstarted, it has two problem,
1 the system stop at creating the partition table, so I have to manually
confirm and moving forward, it seems zerombr and clearpart configuration
didn't work, it should be unattended as expected.
2 after the system was installed, I checked the partition table, one of the
logic vol is gone, here is what I get from anaconda-ks.cfg
#part /boot --fstype=ext4 --size=500
#part pv.008002 --grow --size=1
#volgroup vg_goldstan --pesize=4096 pv.008002
#logvol /home --fstype=ext4 --name=lv_home --vgname=vg_goldstan --grow
–size=100
#logvol / --fstype=ext4 --name=lv_root --vgname=vg_goldstan --grow
–size=1024 --maxsize=51200
#logvol swap --name=lv_swap --vgname=vg_goldstan --grow --size=32248
–maxsize=32248
why they looks so different, did I do something wrong?
Thanks
Sinux
Once again, it seems that foreman didn't read the partition table snippet I
configured and assigned to the host, any one has any idea?
···
On Friday, November 7, 2014 6:47:41 PM UTC+8, sinux shen wrote:
>
> Hi all katello/foreman experts,
>
> I have a ptable template written as follows:
> <%#
> kind: ptable
> name: odw_centos_workstation
> oses:
> - CentOS 5
> - CentOS 6
> - CentOS 7
> %>
> zerombr
> clearpart --all --initlabel
>
> part /boot --fstype=ext4 --size=500
> part pv.1 --grow --size=1
> volgroup vg_system --pesize=4096 pv.1
> logvol / --fstype=ext4 --name=lv_root --vgname=vg_system --size=1024
> --maxsize=51200
> logvol swap --name=lv_swap --vgname=vg_system --size=8000 --maxsize=8000
> logvol /srv/scratch --fstype=ext4 --name=lv_tmp --vgname=vg_system --grow
> --size=1024
>
> but when the system was kickstarted, it has two problem,
> 1 the system stop at creating the partition table, so I have to manually
> confirm and moving forward, it seems zerombr and clearpart configuration
> didn't work, it should be unattended as expected.
> 2 after the system was installed, I checked the partition table, one of
> the logic vol is gone, here is what I get from anaconda-ks.cfg
> #part /boot --fstype=ext4 --size=500
> #part pv.008002 --grow --size=1
> #volgroup vg_goldstan --pesize=4096 pv.008002
> #logvol /home --fstype=ext4 --name=lv_home --vgname=vg_goldstan --grow
> --size=100
> #logvol / --fstype=ext4 --name=lv_root --vgname=vg_goldstan --grow
> --size=1024 --maxsize=51200
> #logvol swap --name=lv_swap --vgname=vg_goldstan --grow --size=32248
> --maxsize=32248
>
> why they looks so different, did I do something wrong?
>
> Thanks
> Sinux
>
I did some more test, if I put the partition content directly into the
provision template, it works, but if I use the same content in a ptable and
called by a host definition, it doesn't, will it be a bug?
···
On Friday, November 7, 2014 6:47:41 PM UTC+8, sinux shen wrote:
>
> Hi all katello/foreman experts,
>
> I have a ptable template written as follows:
> <%#
> kind: ptable
> name: odw_centos_workstation
> oses:
> - CentOS 5
> - CentOS 6
> - CentOS 7
> %>
> zerombr
> clearpart --all --initlabel
>
> part /boot --fstype=ext4 --size=500
> part pv.1 --grow --size=1
> volgroup vg_system --pesize=4096 pv.1
> logvol / --fstype=ext4 --name=lv_root --vgname=vg_system --size=1024
> --maxsize=51200
> logvol swap --name=lv_swap --vgname=vg_system --size=8000 --maxsize=8000
> logvol /srv/scratch --fstype=ext4 --name=lv_tmp --vgname=vg_system --grow
> --size=1024
>
> but when the system was kickstarted, it has two problem,
> 1 the system stop at creating the partition table, so I have to manually
> confirm and moving forward, it seems zerombr and clearpart configuration
> didn't work, it should be unattended as expected.
> 2 after the system was installed, I checked the partition table, one of
> the logic vol is gone, here is what I get from anaconda-ks.cfg
> #part /boot --fstype=ext4 --size=500
> #part pv.008002 --grow --size=1
> #volgroup vg_goldstan --pesize=4096 pv.008002
> #logvol /home --fstype=ext4 --name=lv_home --vgname=vg_goldstan --grow
> --size=100
> #logvol / --fstype=ext4 --name=lv_root --vgname=vg_goldstan --grow
> --size=1024 --maxsize=51200
> #logvol swap --name=lv_swap --vgname=vg_goldstan --grow --size=32248
> --maxsize=32248
>
> why they looks so different, did I do something wrong?
>
> Thanks
> Sinux
>
>
Okey, I got it fixed, it's my bad, for some reason, I missed this important
part:
<% if @dynamic -%>
%include /tmp/diskpart.cfg
<% else -%>
<%= @host.diskLayout %>
<% end -%>
···
On Friday, November 7, 2014 6:47:41 PM UTC+8, sinux shen wrote:
>
> Hi all katello/foreman experts,
>
> I have a ptable template written as follows:
> <%#
> kind: ptable
> name: odw_centos_workstation
> oses:
> - CentOS 5
> - CentOS 6
> - CentOS 7
> %>
> zerombr
> clearpart --all --initlabel
>
> part /boot --fstype=ext4 --size=500
> part pv.1 --grow --size=1
> volgroup vg_system --pesize=4096 pv.1
> logvol / --fstype=ext4 --name=lv_root --vgname=vg_system --size=1024
> --maxsize=51200
> logvol swap --name=lv_swap --vgname=vg_system --size=8000 --maxsize=8000
> logvol /srv/scratch --fstype=ext4 --name=lv_tmp --vgname=vg_system --grow
> --size=1024
>
> but when the system was kickstarted, it has two problem,
> 1 the system stop at creating the partition table, so I have to manually
> confirm and moving forward, it seems zerombr and clearpart configuration
> didn't work, it should be unattended as expected.
> 2 after the system was installed, I checked the partition table, one of
> the logic vol is gone, here is what I get from anaconda-ks.cfg
> #part /boot --fstype=ext4 --size=500
> #part pv.008002 --grow --size=1
> #volgroup vg_goldstan --pesize=4096 pv.008002
> #logvol /home --fstype=ext4 --name=lv_home --vgname=vg_goldstan --grow
> --size=100
> #logvol / --fstype=ext4 --name=lv_root --vgname=vg_goldstan --grow
> --size=1024 --maxsize=51200
> #logvol swap --name=lv_swap --vgname=vg_goldstan --grow --size=32248
> --maxsize=32248
>
> why they looks so different, did I do something wrong?
>
> Thanks
> Sinux
>
>