RedHat installation via fai

[Denny Bortfeldt]

Hello everyone,

we did manage to install debian, sles (via autoyast) and centos (base-file)
via fai.
But now we need also install RedHat.
Did anyone manage to install RedHat via fai? If yes, how? Is there a
basefile which could be shared?

Thanks in advance.

Best regards,
Denny

Re: scripts don't execute

[Denny Bortfeldt]

Can you upload your fai.log, shell.log and an output of your scripts folder?

2016-06-24 18:48 GMT+02:00 Ronald Steele <rste...@adaptivemethods.com>:

> Yes, it’s excitable. That was my first thought too.
> ls -l reports
> -rwxr-xr-x 1 root root …
>
> The same permissions are on the directory, which matches all the other
> script directories.
>
> Ron
>
>
> On Jun 24, 2016, at 10:16 AM, Denny Bortfeldt <de...@bortfeldt.net> wrote:
>
> Are you sure that your script in /- got chmod +x ?
> Without execution flag the script will not get executed.
>
> 2016-06-24 15:59 GMT+02:00 Ronald Steele <rste...@adaptivemethods.com>:
>
>> I’m trying to use scripts to install application software.   The scripts
>> never get executed.
>> If I embed the same script code into to one of the existing scripts (say
>> CENTOS) the code works, however any scripts I create are never executed.
>> The script’s file permissions are the same as the existing scripts.  The
>> class name is defined in .../class/50-host-classes and appears in the log
>> files in variables.log and fai.log (but never in shell.log).
>>
>> Thanks for any ideas.
>>
>> Ron
>>
>>
>>
> --
>
> Spam
> <https://antispam.roaringpenguin.com/canit/b.php?i=0aRaCgUWx=114e6b607ad9=20160624=s>
> Phish/Fraud
> <https://antispam.roaringpenguin.com/canit/b.php?i=0aRaCgUWx=114e6b607ad9=20160624=p>
> Not spam
> <https://antispam.roaringpenguin.com/canit/b.php?i=0aRaCgUWx=114e6b607ad9=20160624=n>
> Forget previous vote
> <https://antispam.roaringpenguin.com/canit/b.php?i=0aRaCgUWx=114e6b607ad9=20160624=f>
>
>
>

Re: scripts don't execute

[Denny Bortfeldt]

Are you sure that your script in /- got chmod +x ? Without
execution flag the script will not get executed.

2016-06-24 15:59 GMT+02:00 Ronald Steele :

> I’m trying to use scripts to install application software.   The scripts
> never get executed.
> If I embed the same script code into to one of the existing scripts (say
> CENTOS) the code works, however any scripts I create are never executed.
> The script’s file permissions are the same as the existing scripts.  The
> class name is defined in .../class/50-host-classes and appears in the log
> files in variables.log and fai.log (but never in shell.log).
>
> Thanks for any ideas.
>
> Ron
>
>
>

AW: AW: AW: AW: AW: Problem with virtio network boot

[Denny Bortfeldt]

Hello everyone,

I could fix the problem. And here's the solution if you also got the problem:

VirtIO driver is included in the initrd, but when the VM boot into dracut the 
"dhclient" command fails. This happens, because of bad checksums with special 
software.
Currently we use qemu/kvm on out virtualization host and create the vms with 
"virt-install" and parameter "--pxe" for netboot. 
During netboot our DHCP-Server (dnsmasq) give the client an IP and this 
dnsserver got a little bug which was fixed in isc-dhcp already (standard dhcp 
in fai-installation). So nearly everyone should not have the same problem.

There are some solutions to fix the bad checksums bug:
- use isc-dhcp
- use e1000 driver instead during installation
- use an iptables-rule on the virtualization host(!!)
-- iptables -A POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM 
--checksum-fill

Bug-Links:
- https://forge.univention.org/bugzilla/show_bug.cgi?id=33160 & 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717215

A special thanks to Thomas, who helped me a lot with nice hints!

Best regards,
Denny

AW: AW: AW: AW: Problem with virtio network boot

[Denny Bortfeldt]

Default timeout are 20 seconds, this is way enough. DHCPOFFERS will be send out 
but VM don't respect them.
This problem only occur with Dracut and virtio network card.

With FAI 3 everything worked fine.

AW: AW: AW: Problem with virtio network boot

[Denny Bortfeldt]

Screenshot attached:
https://data.bortfeldt.net/f/84d501dcd7/


Don't know why the interface can't get started.

Jun 14 17:57:45 s110077 dnsmasq-dhcp[1840]: DHCPDISCOVER(eth1) 52:54:00:81:ff:41
Jun 14 17:57:45 s110077 dnsmasq-dhcp[1840]: DHCPOFFER(eth1) 10.0.100.108 
52:54:00:81:ff:41
Jun 14 17:57:52 s110077 dnsmasq-dhcp[1840]: DHCPDISCOVER(eth1) 52:54:00:81:ff:41
Jun 14 17:57:52 s110077 dnsmasq-dhcp[1840]: DHCPOFFER(eth1) 10.0.100.108 
52:54:00:81:ff:41
Jun 14 17:58:06 s110077 dnsmasq-dhcp[1840]: DHCPDISCOVER(eth1) 52:54:00:81:ff:41
Jun 14 17:58:06 s110077 dnsmasq-dhcp[1840]: DHCPOFFER(eth1) 10.0.100.108 
52:54:00:81:ff:41
Jun 14 17:58:26 s110077 dnsmasq-dhcp[1840]: DHCPDISCOVER(eth1) 52:54:00:81:ff:41
Jun 14 17:58:26 s110077 dnsmasq-dhcp[1840]: DHCPOFFER(eth1) 10.0.100.108 
52:54:00:81:ff:41
DHCPOFFERS also send out all the time.

AW: AW: Problem with virtio network boot

[Denny Bortfeldt]

>> but only DHCP is not working
Yes and no. It's only not working when booting with virtio network card when 
dracut is running.
The first DHCP request for pxe-boot-menu is received successfully. After that 
the initrd and stuff is loaded.
When dracut is running a dhcp again, then the dhcp fails - I also don't see any 
traffic anymore from the vm.

When I boot with any other card then everything works fine.
So I don't think there is a problem with the dhcp-server because if there would 
one, then also the initial dhcp request would not get an IP and therefore the 
boot menu wouldn't appear.


Best regards,
Denny

AW: Problem with virtio network boot

[Denny Bortfeldt]

Hey,

/srv/tftp/fai# lsinitrd initrd.img-3.16.0-4-amd64  | grep virtio
-rw-r--r--   1 root root25872 Apr  9 00:54 
lib/modules/3.16.0-4-amd64/kernel/drivers/block/virtio_blk.ko
-rw-r--r--   1 root root51376 Apr  9 00:54 
lib/modules/3.16.0-4-amd64/kernel/drivers/net/virtio_net.ko
-rw-r--r--   1 root root28240 Apr  9 00:54 
lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/virtio_scsi.ko
drwxr-xr-x   2 root root0 Jun 13 16:26 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio
-rw-r--r--   1 root root13512 Apr  9 00:54 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio/virtio.ko
-rw-r--r--   1 root root20200 Apr  9 00:54 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio/virtio_pci.ko
-rw-r--r--   1 root root22608 Apr  9 00:54 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio/virtio_ring.ko

Drivers are included.

-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas 
Lange
Gesendet: Dienstag, 14. Juni 2016 17:18
An: fully automatic installation for Linux
Betreff: Re: Problem with virtio network boot

>>>>> On Tue, 14 Jun 2016 15:09:49 +, Denny Bortfeldt 
>>>>> <d.bortfe...@babiel.com> said:

> When I create the VM with an e1000 driver everything works fine.
> We didn’t have this problem with FAI 3, this now happens with FAI 5.

> Seems like dracut don’t support virtio out of the box?
Yes, it should support virtio devices. Use this to check if the drivers are 
included into the initrd.

> lsinitrd /srv/fai/nfsroot/boot/initrd.img-3.16.0-4-amd64
-rw-r--r--   1 root root25872 Mar  9 05:42 
lib/modules/3.16.0-4-amd64/kernel/drivers/block/virtio_blk.ko
-rw-r--r--   1 root root51376 Mar  9 05:41 
lib/modules/3.16.0-4-amd64/kernel/drivers/net/virtio_net.ko
-rw-r--r--   1 root root28240 Mar  9 05:41 
lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/virtio_scsi.ko
drwxr-xr-x   2 root root0 Apr 15 14:33 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio
-rw-r--r--   1 root root13512 Mar  9 05:41 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio/virtio.ko
-rw-r--r--   1 root root20200 Mar  9 05:41 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio/virtio_pci.ko
-rw-r--r--   1 root root22608 Mar  9 05:41 
lib/modules/3.16.0-4-amd64/kernel/drivers/virtio/virtio_ring.ko


--
regards Thomas

Problem with virtio network boot

[Denny Bortfeldt]

Hello everyone,

I’ve got a little problem with virtio vms.
When I create a new vm with a virtio network card, then the system will get an 
IP for PXE-Boot, the menu appears and after loading the initrd and vmlinuz, the 
system hang at:

„Starting dhcp for interface eth0
dhcp: PREINIT eth0 up
dhcp: FAIL
dhcp failed
RTNETLINK answers: File exists“

When I create the VM with an e1000 driver everything works fine.
We didn’t have this problem with FAI 3, this now happens with FAI 5.

Seems like dracut don’t support virtio out of the box?


Best regards,
Denny

AW: Problem with DNS DHCP-Name

[Denny Bortfeldt]

Thank you Thomas!

-Ursprüngliche Nachricht-
Von: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] Im Auftrag von Thomas 
Lange
Gesendet: Montag, 13. Juni 2016 15:19
An: fully automatic installation for Linux
Betreff: Re: Problem with DNS DHCP-Name

>>>>> On Mon, 13 Jun 2016 12:52:54 +, Denny Bortfeldt 
>>>>> <d.bortfe...@babiel.com> said:

> Hello everyone,
> I’ve got a little problem with my fai installations.

> Everytime I install a client via pxe, the name of the vm contains our dns 
domain. I know that Thomas had a fix for this but I can’t find it anywhere.

> Can anyone give me a link or a hint for the fix?

cat <> /srv/fai/nfsroot/etc/fai/fai.conf # use short hostname instead of 
FQDN export HOSTNAME=\${HOSTNAME%%.*} echo \$HOSTNAME > 
/proc/sys/kernel/hostname EOF


--
regards Thomas

Problem with DNS DHCP-Name

[Denny Bortfeldt]

Hello everyone,

I’ve got a little problem with my fai installations.
Everytime I install a client via pxe, the name of the vm contains our dns 
domain. I know that Thomas had a fix for this but I can’t find it anywhere.
Can anyone give me a link or a hint for the fix?

For example:
DNS-Domain: domain.tld
VM-Name via DHCP: f00

Name of vm during installation would be: f00.domain.tld


Thanks in advance.

Best regards,
Denny

Re: Problem with GPT Bios Partition

[Denny Bortfeldt]

Hello everyone,

just a follow-up. With the help from Kerim I could managed my setup.
The disk-label "gpt-bios" will create this special 2MB Bios-Partition at
the end of the part-layout. It's not neccessary to define it in the
disk_config-File.

So to create my layout as I mention in the first mail my disk_config looks
like this now:


#

disk_config disk1 disklabel:gpt-bios bootable:3 fstabkey:uuid

primary swap 8192 swap rw
primary /boot 512 ext4 rw,noatime,errors=remount-ro
primary / 15360 ext4 rw,noatime,errors=remount-ro




Thanks everyone for helping me out!


Best regards,
Denny


2015-11-26 18:39 GMT+01:00 Kerim Gueney <kgue...@uni-koeln.de>:

> Hey Denny,
>
> Type 4 is 16-bit FAT (up to 32M), I see there's some Microsoft partitions.
> Is the first partition perhaps an MBR that was installed along some
> previous Windows installation? I only ever see it when I installed Windows
> on my machine prior to Linux. Maybe you could do the following:
>
> disk_config disk1 disklabel:gpt-bios bootable:1 fstabkey:uuid
> primary - 2048 msdos rw # (msdos is fat16)
> primary swap 8192 swap rw
> primary /boot 512 ext4 rw,noatime,errors=remount-ro
> primary / 15360 ext4 rw,noatime,errors=remount-ro
> logical - 1- - -
>
>
> Best regards
> Kerim
>
>
>
> On 26.11.2015 18:14, Denny Bortfeldt wrote:
>
> Hey Kerim,
>
> no not really - my disk_config could be/is wrong.
> The following schema need to be created by FAI disk_config:
>
> GPT /dev/sda1 2048 6143 2M BIOS boot partition /dev/sda2 6144 16783359 8G
> Linux swap /dev/sda3 16783360 17831935 512M Microsoft basic data /boot
> /dev/sda4 17831936 49289215 15G Microsoft basic data / /dev/sda5 49289216
> 7812456414 3.6T Linux LVM
>
> But here's the problem: I don't know how.
> The /dev/sda1 partition don't have got a mount point and is a type "4" in
> fdisk/gdisk - so I don't know what I need to write in my disk_config so
> that FAI will use "type 4" in partition layout.
> /dev/sda2, /dev/sda3 and /dev/sda4 is clear - everything is "primary" and
> swap or ext4.
>
>
> So what do I need to enter in my disk_config that the result will look
> like:
>
> /dev/sda1 2048 6143 2M BIOS boot partition
>
> Thanks in advance :)
>
> Best regards,
> Denny
>
> 2015-11-26 17:48 GMT+01:00 Kerim Güney <kgue...@uni-koeln.de>:
>
>> Hi Denny,
>>
>> there seems to be a mismatch of sorts between your desired schema and
>> what you're actually describing. I am going to assume you want an EFI
>> partition that you're going to boot off of.
>>
>> To do so, this should work:
>>
>> disk_config disk1 disklabel:gpt-bios bootable:1 fstabkey:uuid
>>
>> primary /boot/efi 2048 vfat rw
>> primary swap 8192 swap rw
>> primary /boot 512 ext4 rw,noatime,errors=remount-ro
>> primary / 15360 ext4 rw,noatime,errors=remount-ro
>> logical - 1- - -
>>
>>
>> Best regards
>> Kerim
>>
>>
>> On 26/11/15 16:19, Denny Bortfeldt wrote:
>>
>> Hello everyone,
>>
>> I'm using FAI 5.0 and need a special partition layout for our centos kvm
>> installation.
>>
>> The partition schema need to be like this:
>>
>> GPT /dev/sda1 2048 6143 2M BIOS boot partition /dev/sda2 6144 16783359 8G
>> Linux swap /dev/sda3 16783360 17831935 512M Microsoft basic data /boot
>> /dev/sda4 17831936 49289215 15G Microsoft basic data / /dev/sda5 49289216
>> 7812456414 3.6T Linux LVM
>> Unfortunately I'm unable to create /dev/sda1 and /dev/sda5 with the
>> disk_config.
>> I don't know what "fstype" I have to enter, that FAI will partitionate
>> /dev/sda1 to "BIOS boot partition" (fdisk type "4").
>> fstype "efi" and "bios" will run into an error:
>> https://data.bortfeldt.net/f/d9b3239df0/
>> My current config_disk-File looks like this:
>> #
>>
>> disk_config disk1 disklabel:gpt-bios bootable:3 fstabkey:uuid
>>
>> primary - 2 efi -
>> primary swap 8192 swap rw
>> primary /boot 512 ext4 rw,noatime,errors=remount-ro
>> primary / 15360 ext4 rw,noatime,errors=remount-ro
>> logical - 1- - -
>>
>>
>> So is anyone here who can help me out with my disk_configuration so that
>> FAI will partitionate like the schema above?
>>
>> Thanks in advance.
>>
>> Best regards,
>> Denny
>>
>>
>> --
>>  Kerim Güney
>>
>>  Institut für InformatikJunior Sysadmin
>>  Universität zu KölnLehrstuhl Prof. Dr. M. Jünger
>> Weyertal 121
>>   50931 Köln
>>
>>
>
>

Problem with GPT Bios Partition

[Denny Bortfeldt]

Hello everyone,

I'm using FAI 5.0 and need a special partition layout for our centos kvm
installation.

The partition schema need to be like this:

GPT /dev/sda1 2048 6143 2M BIOS boot partition /dev/sda2 6144 16783359 8G
Linux swap /dev/sda3 16783360 17831935 512M Microsoft basic data /boot
/dev/sda4 17831936 49289215 15G Microsoft basic data / /dev/sda5 49289216
7812456414 3.6T Linux LVM


Unfortunately I'm unable to create /dev/sda1 and /dev/sda5 with the
disk_config.

I don't know what "fstype" I have to enter, that FAI will partitionate
/dev/sda1 to "BIOS boot partition" (fdisk type "4").
fstype "efi" and "bios" will run into an error:
https://data.bortfeldt.net/f/d9b3239df0/


My current config_disk-File looks like this:

#

disk_config disk1 disklabel:gpt-bios bootable:3 fstabkey:uuid

primary - 2 efi -
primary swap 8192 swap rw
primary /boot 512 ext4 rw,noatime,errors=remount-ro
primary / 15360 ext4 rw,noatime,errors=remount-ro
logical - 1- - -


So is anyone here who can help me out with my disk_configuration so that
FAI will partitionate like the schema above?

Thanks in advance.

Best regards,
Denny

Re: Problem with mk-basefile

[Denny Bortfeldt]

>> btw I am online
Seems like you're on the wrong server.
Try using irc.oftc.net.

2015-11-26 17:00 GMT+01:00 Werner Pommerer :

> rpm2cpio was installed. During the following actions,
> I lost the package rinse. But, when I try now:
>
> apt-get install rinse
>
> I get:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  rinse : Depends: cpio (>= 2.11+dfsg-4.1) but 2.11+dfsg-0.1+deb7u1 is to
> be installed
> E: Unable to correct problems, you have held broken packages.
>
> I do not understand, what happened.
> btw I am online
>
>
> Regards
>
> Zitat von Thomas Lange :
>
> On Thu, 26 Nov 2015 16:28:45 +0100, Werner Pommerer <
>>> werner.pomme...@uni-hohenheim.de> said:
>>>
>>
>> > I joined the #fai channel nickname pommerer. But I am not shure
>> > how to use it.
>> You are not online at the moment.
>>
>>
>> > In the meantime: the answer
>> > ./mk-basefile -J CENTOS7_64
>>
>> > Extracting: filesystem-3.2-18.el7.x86_64.rpm
>> > failed to extract filesystem-3.2-18.el7.x86_64.rpm: 16384
>> cmd:
>> > rpm2cpio
>> /var/tmp/basefiles.u4JkGb1u/filesystem-3.2-18.el7.x86_64.rpm
>> > | (cd /var/tmp/basefiles.u4JkGb1u ; cpio --extract
>> > --extract-over-symlinks --make-directories --no-absolute-filenames
>> > --preserve-modification-time) 2>/dev/null >/dev/null at
>> > /usr/sbin/rinse line 1156.
>> OK, I guess you have to install the package rpm2cpio.
>> There's a missing dependency in the rinse package, that I have to
>> fix.
>>
>> --
>> regards Thomas
>>
>
>
>
>

Re: Problem with GPT Bios Partition

[Denny Bortfeldt]

Hey Kerim,

no not really - my disk_config could be/is wrong.
The following schema need to be created by FAI disk_config:

GPT /dev/sda1 2048 6143 2M BIOS boot partition /dev/sda2 6144 16783359 8G
Linux swap /dev/sda3 16783360 17831935 512M Microsoft basic data /boot
/dev/sda4 17831936 49289215 15G Microsoft basic data / /dev/sda5 49289216
7812456414 3.6T Linux LVM

But here's the problem: I don't know how.
The /dev/sda1 partition don't have got a mount point and is a type "4" in
fdisk/gdisk - so I don't know what I need to write in my disk_config so
that FAI will use "type 4" in partition layout.
/dev/sda2, /dev/sda3 and /dev/sda4 is clear - everything is "primary" and
swap or ext4.


So what do I need to enter in my disk_config that the result will look like:

/dev/sda1 2048 6143 2M BIOS boot partition

Thanks in advance :)

Best regards,
Denny

2015-11-26 17:48 GMT+01:00 Kerim Güney <kgue...@uni-koeln.de>:

> Hi Denny,
>
> there seems to be a mismatch of sorts between your desired schema and what
> you're actually describing. I am going to assume you want an EFI partition
> that you're going to boot off of.
>
> To do so, this should work:
>
> disk_config disk1 disklabel:gpt-bios bootable:1 fstabkey:uuid
>
> primary /boot/efi 2048 vfat rw
> primary swap 8192 swap rw
> primary /boot 512 ext4 rw,noatime,errors=remount-ro
> primary / 15360 ext4 rw,noatime,errors=remount-ro
> logical - 1- - -
>
>
> Best regards
> Kerim
>
>
> On 26/11/15 16:19, Denny Bortfeldt wrote:
>
> Hello everyone,
>
> I'm using FAI 5.0 and need a special partition layout for our centos kvm
> installation.
>
> The partition schema need to be like this:
>
> GPT /dev/sda1 2048 6143 2M BIOS boot partition /dev/sda2 6144 16783359 8G
> Linux swap /dev/sda3 16783360 17831935 512M Microsoft basic data /boot
> /dev/sda4 17831936 49289215 15G Microsoft basic data / /dev/sda5 49289216
> 7812456414 3.6T Linux LVM
> Unfortunately I'm unable to create /dev/sda1 and /dev/sda5 with the
> disk_config.
> I don't know what "fstype" I have to enter, that FAI will partitionate
> /dev/sda1 to "BIOS boot partition" (fdisk type "4").
> fstype "efi" and "bios" will run into an error:
> https://data.bortfeldt.net/f/d9b3239df0/
> My current config_disk-File looks like this:
> #
>
> disk_config disk1 disklabel:gpt-bios bootable:3 fstabkey:uuid
>
> primary - 2 efi -
> primary swap 8192 swap rw
> primary /boot 512 ext4 rw,noatime,errors=remount-ro
> primary / 15360 ext4 rw,noatime,errors=remount-ro
> logical - 1- - -
>
>
> So is anyone here who can help me out with my disk_configuration so that
> FAI will partitionate like the schema above?
>
> Thanks in advance.
>
> Best regards,
> Denny
>
>
> --
>  Kerim Güney
>
>  Institut für InformatikJunior Sysadmin
>  Universität zu KölnLehrstuhl Prof. Dr. M. Jünger
> Weyertal 121
>   50931 Köln
>
>

Problem with CentOS 7 PXE Install

[Denny Bortfeldt]

Hello,

I've got a little problem with the CentOS PXE Installation.
My DHCP/PXE-Server is configured and I'm able to select the
centos-installation in the pxe menu. FAI also extract the base-tgz and
update the system. But after rebooting the CentOS-Systeme, there are wrong
permissions for "/", which are 700 and therefore no user (except for root)
is able to login.
Now my question: Why are there wrong permissions? Is this wrong in the tgz
or is there any process, hook, script which changed them?


Thank you very much in advance.

Best regards,
Denny

Re: Problem with CentOS 7 PXE Install

[Denny Bortfeldt]

Hello everyone,

I could fix this issue together with Thomas.
I'm using a wheezy installation of FAI and this version have got an old
version of CENTOS/10-security script.
If you replace this with the one from
https://github.com/faiproject/fai/tree/master/examples/simple/scripts/CENTOS
then everything works like a charm.

Thank you Thomas!

Greetings,
Denny (d3nny)

2015-10-28 13:29 GMT+01:00 Thomas Lange <la...@informatik.uni-koeln.de>:

> >>>>> On Wed, 28 Oct 2015 13:07:10 +0100, Denny Bortfeldt <
> de...@bortfeldt.net> said:
>
> > I've got a little problem with the CentOS PXE Installation.
> > My DHCP/PXE-Server is configured and I'm able to select the
> > centos-installation in the pxe menu.
> Which FAI version are you using? Which PXE menu do you mean? By
> default, there's no PXE menu in FAI.
>
>
> > FAI also extract the base-tgz and update the system. But after
> rebooting the CentOS-Systeme,
> > there are wrong permissions for "/", which are 700 and therefore no
> user (except for root) is able to login.
> > Now my question: Why are there wrong permissions? Is this wrong in
> the tgz or is there any process, hook, script which changed them?
> By default when doing a CentOS 7 installation with FAI, during the
> first boot of the new system, the system will fix some
> attributes/permission on the file systems. Maybe this is not working?
>
>
> Can you please put the fai.log and shell.log of your installation onto
> paste.debian.net. If you join the irc channel #fai I can help you much
> faster.
> --
> regards Thomas
>

Re: What is renaming my PXE files?

[Denny Bortfeldt]

You don't need to edit the source code. You can create a hook for this task
and at the end skip the task so that the normal subroutine won't execute
anymore.

2015-08-05 0:01 GMT+02:00 John G Heim jh...@math.wisc.edu:



 On 07/24/2015 05:18 PM, Thomas Lange wrote:

 On Fri, 24 Jul 2015 11:05:33 -0500, John G Heim jh...@math.wisc.edu
 said:


   After my FAI install finishes, the PXE boot config file gets
 renamed to
   something.disable. I am guessing fai does that somehow. Can I
 disable
   that?
 task chboot is logging into the install server and calls fai-chboot
 which disables the pxe config.

 You may redefine the subroutine task_chboot, or undefine LOGUSER or
 set $FAI_LOGPROTO to none. But this will also disable saving the log
 files to your install server.


 When you say redefine the subroutine task_chboot, I take it you mean
 edit the fai source code, right? Or can you redefine a task subroutine some
 other way? I see in the documentation that tasks are defined in
 /usr/lib/fai/subroutines. I think I can edit that to fix my problem. But
 whatever changes I make will be wiped out if I rebuild the nfsroot, right?

Problem with CentOS 7 Installation

[Denny Bortfeldt]

Hello everyone,

 

I tried now several hours to create an unattended centos installation with
fai.

I've got already a working fai with debian wheezy  jessie and now I wanted
to integrate also CentOS.

 

I downloaded the basefile (CENTOS7_x86_64) and put them in $FAI/basefiles
folder. The class is also set and the archive will successfully extracted
within the installation.

But after the extration of the basefile every script and hook will false. I
have to admit, that I use an internal ip which is not routeable and won't
get connection to the internet. All repositories are accessable via local
dns server and local ips (for example debian mirror will resolve into
192.168.0.100)

 

Anyway, after installation the hook updatebase.CENTOS will executed and
the following yum update fail for no reason (client only download
repo/repodata.xml and nothing more) - therefore the whole server won't
update/install any packages.

Now my question:

-  What special nfsroot do I need? Currently my CentOS Installation
use the same nfsroot as for debian (is here the error??)

-  OT: CentOS-Specific: Why the hack the client only download
repo/repodata.xml and output an error afterwards: no baseurl for base/7/
could found?

 

Thank you very much in advance.

Best regards,

Denny