RedHat installation via fai
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: RedHat installation via fai
> On Tue, 9 Aug 2016 09:24:55 +0200, Denny Bortfeldt > said: > Did anyone manage to install RedHat via fai? If yes, how? Is there a basefile which could be shared? No, there's no basefile for Redhat. Since RHEL has a commercial lizence, I cannot distribute basefiles for it. You have to build your own using the mk-basefile script which is included in FAI. But it should be very easy, since everything will work the same way as with CentOS. -- regards Thomas
/tmp read-only with stretch and FAI 5.1.2
I am just starting to look at Debian stretch and FAI 5.1.2. I have an FAI server installed with all stock Debian stretch packages and am trying to use dracut with overlayfs. When I boot a client to install stretch via FAI, all of the filesystems appear to mount properly, including the nfsroot. However, /tmp is not writeable. I can write to / though. Has anyone else seen this problem? Here is more info on my setup: FAI package version:5.1.2 Dracut package version: 044+105-2 Kernel package version: 4.6.4-1 On the install client: Command line: BOOT_IMAGE=vmlinuz-4.6.0-1-amd64 initrd=initrd.img-4.6.0-1-amd64 rw rootovl ip=eth0:dhcp root=nfs:faiserver:/srv/fai/nfsroot FAI_FLAGS=verbose,sshd,createvt FAI_CONFIG_SRC=nfs://faiserver/srv/fai/config FAI_ACTION=install root@faiclient:~# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 230M 0 230M 0% /dev tmpfs247M 280K 247M 1% /run overlay 247M 0 247M 0% / tmpfs247M 0 247M 0% /live/cow faiserver:/srv/fai/nfsroot30G 4.1G 24G 15% /live/image faiserver:/srv/fai/config 30G 4.1G 24G 15% /var/lib/fai/config root@faiclient:~# lsmod | grep overlay overlay45056 1 root@faiclient:~# touch /tmp/test touch: cannot touch '/tmp/test': Operation not supported root@faiclient:~# touch /test root@faiclient:~# Thanks in advance for any help or suggestions for fixing the problem. Jeff Stolte
Re: /tmp read-only with stretch and FAI 5.1.2
> On Tue, 9 Aug 2016 10:10:35 -0600, Jeffrey Stolte said: > root@faiclient:~# touch /tmp/test > touch: cannot touch '/tmp/test': Operation not supported Strange. This does not look like a permissions denied message. I do not have this problem. Check if the permissions of your /tmp inside the nfsroot are set like this: ls -al /srv/fai/nfsroot/tmp/ drwxrwxrwt+ 2 root root 4096 Jul 1 17:44 . -- regards Thomas
Re: /tmp read-only with stretch and FAI 5.1.2
On Tue, Aug 09, 2016 at 08:43:19PM +0200, Thomas Lange wrote: > > Strange. This does not look like a permissions denied message. > I do not have this problem. Check if the permissions of your > /tmp inside the nfsroot are set like this: > > ls -al /srv/fai/nfsroot/tmp/ > drwxrwxrwt+ 2 root root 4096 Jul 1 17:44 . Thomas, The permissions are similar, but it looks like you have additional ACLs enabled (the '+' symbol in the ls output above). Do you know if that is necessary? Here's the ls output from my server: faiserver:~# ls -al /srv/fai/nfsroot/tmp/ total 8 drwxrwxrwt 2 root root 4096 Aug 8 16:22 ./ drwxr-xr-x 21 root root 4096 Aug 8 16:21 ../ Thanks. Jeff
Re: /tmp read-only with stretch and FAI 5.1.2
I do not know if the ACLs are needed. I've uploaded a tar ball of a generic nfsroot (stretch, FAI 5.1.2, kernel 4.6) to http://fai-project.org/download/misc/nfsroot-generic_5.1.2_4.6.tar.xz It was created by fai-make-nfsroot -fvg You can extract it on your FAI server and adjust it by calling fai-make-nfsroot -av See the man page for details. Then copy the kernel and initrd from the nfsroot to your tftp location. This nfsroot work perfectly in my network. Please report if this also works for you. best regards thomas
Re: Not-so-predictable network names
On Fri, Aug 5, 2016, at 06:59 AM, Alexander Thomas wrote: > This assumes the first interface shown by lshw is the one you want, > which was the case on the few systems I tried this on. Your mileage > may vary :) fyi: on my machine the first is the wrong one.
Re: Not-so-predictable network names
On Thu, Aug 4, 2016, at 08:52 AM, andrew bezella wrote: > > why slot and not port: > > Working from top to bottom, udev takes the first match of: > > > > * ID_NET_NAME_FROM_DATABASE > > * ID_NET_NAME_ONBOARD > > * ID_NET_NAME_SLOT > > * ID_NET_NAME_PATH > > * ID_NET_NAME_MAC > > cf. > https://major.io/2015/08/21/understanding-systemds-predictable-network-device-names/ > > hth... Yes, I'm following this path. At the top of 30-interface, I have a condition for if the os is in a class that uses a persistent name, and inside I have this code: for field in ID_NET_NAME_FROM_DATABASE \ ID_NET_NAME_ONBOARD \ ID_NET_NAME_SLOT \ ID_NET_NAME_PATH \ ID_NET_NAME_MAC; do name=$(udevadm info /sys/class/net/$NIC1 | sed -rn "s/^E: $field=(.+)/\1/p") if [[ $name ]]; then NIC1=$name break fi done if [[ ! $name ]]; then echo "$0: error: could not find systemd predictable network name" exit 1 fi
Re: example network script will misname interface if installing stretch
On Mon, Jul 18, 2016, at 01:38 AM, Thomas Lange wrote: > > On Sat, 16 Jul 2016 14:18:25 -0700, Ian Kelling > > said: > > > Using jessie as the base os to install stretch. > > 30-interface will setup /etc/network/interfaces with > > something like eth0, and if you upgrade to stretch, > > it will reboot and eth0 is now named something like > > enp3s0f1. > This is already fixed in FAI 5.1. > > -- > regards Thomas In case people stumble across this, there are still issues around this, see the thread named "Not-so-predictable network names"
Re: Not-so-predictable network names
On Tue, 2016-08-09 at 14:12 -0700, Ian Kelling wrote: > > Yes, I'm following this path. At the top of 30-interface, I have a > condition > for if the os is in a class that uses a persistent name, and inside > I have this code: [...] oh! i like that solution, thanks for sharing... -- andrew bezella Internet Archive
