From mail at jeffer.ph Wed May 7 12:22:35 2014 From: mail at jeffer.ph (Paul Jefferson) Date: Wed, 07 May 2014 13:22:35 +0100 Subject: Checking dependencies of custom Fedora Spins In-Reply-To: <3527434A537F2F42A53BAA31DC03BB6AC4815A16B8@SERVER1.family.local> References: <1398424500.25372.110294333.23453162@webmail.messagingengine.com> <3527434A537F2F42A53BAA31DC03BB6AC4815A16B8@SERVER1.family.local> Message-ID: <1399465355.8221.114629837.56DDD95D@webmail.messagingengine.com> Hi Kay, Thanks very much for the information. I see that this issue will be addressed in F21 (https://git.fedorahosted.org/cgit/comps.git/commit/?id=33bb568e7dfecb4b8d859b73abec1ca5d24ebdde). The minimal install that you describe made me approach my issue from a different angle. I tried playing around with a few minimal kickstarts in order to replicate the failed dependency issue I was observing. It turns out that my issue was due to packages that I had explicitly excluded from the spin in the kickstart (using the minus operator in the %packages section) that were dependencies of other packages that were being installed. The missing dependencies showed up in the pungi log as warnings, but the tree and subsequent ISO creation processes completed successfully. I'll keep a closer eye on the warnings produced by pungi from here on in. Cheers, Paul -- Paul Jefferson On Fri, Apr 25, 2014, at 04:06 PM, Kay Williams wrote: > I ran into the same issue for rhel7 beta and reported it at > https://bugzilla.redhat.com/show_bug.cgi?id=1040707. That bug seems to > have been made private somewhere along the way, so I've copied the > relevant content below: > > > --------------------- > > Description Kay Williams 2013-12-11 18:42:37 EST > Description of problem: > In previous versions, it was possible to create a custom install tree > including packages from the core group, plus dependencies, plus a kernel > (and any other desired packages). > > This is not working in rhel 7.0 beta because anaconda requires several > packages that are not listed in the core group. Among these packages are > authconfig, chrony, firewalld and grub2. These packages are listed in > other groups as follows: > > authconfig, base > chrony, base > firewalld, base > grub2, anaconda-tools > > For custom install tree creation, it is convenient to have all of the > anaconda requried packages listed in the core group (or else included in > the stage2 install image). > > Version-Release number of selected component (if applicable): > Anaconda 19.31.36 and RHEL 7.0 Beta comps file > > > How reproducible: > Always. > > Steps to Reproduce: > 1. Create a custom install tree containing just packages from the core > group + dependencies + a kernel + dependencies. > 2. Attempt to install using the custom install tree. > > Actual results: > Anaconda fails attempting to install the missing package (authconfig, > chrony, firewalld, or grub2). > > Expected results: > Install completes without error. > > Comment 2 Bill Nottingham 2013-12-12 15:15:17 EST > @anaconda-tools is needed for any custom install distribution, as that is > where bootloaders/filesystem utilities/storage utilities that may be used > depend on your installation type are denoted. > > Comment 3 Kay Williams 2013-12-12 19:30:19 EST > Hi Bill, we tried including both @core and @anaconda-tools in the custom > distribution, but anaconda still fails attempting to install crony and > firewalld. > > In the big picture, ideally there would be a reliable formula for > identifying the minimum set of packages required for a custom > distribution. In the past, we used the formula '@core + a kernel + > dependencies'. > > At the moment, the formula seems to be '@core + @anaconda-tools (which > brings in authconfig, grub2) + some packages from @base (crony, > firewalld) + a kernel + dependencies'. > > Perhaps crony and firewalld (and potentially others?) should be listed in > @anaconda-tools (authconfig is listed in both). > > Or is there another way? One model is to include all the tools needed for > performing installation in the stage2 image. In this model the custom > distribution can include just the packages needed for the end system > without regard for anaconda install requirements. > > Thanks for considering. > > Comment 4 Bill Nottingham 2013-12-13 14:22:28 EST > This seems reasonable. > > Vaclav - can you add chrony, firewalld, and authconfig to @anaconda-tools > in RHEL 7 and Fedora? > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Paul Jefferson > Sent: Friday, April 25, 2014 4:15 AM > To: kickstart-list at redhat.com > Subject: Checking dependencies of custom Fedora Spins > > Hi everyone, > > I am currently in the process of creating a custom spin of Fedora 19 > which will be based on the Fedora Xfce (or MATE) spin. > > I have been through a couple of iterations of: > > * adding packages to the kickstart file > * building the installation tree using pungi (-G -B and -C) > * adding a custom kickstart and isolinux configuration to tree > * building the installation media (pungi -I) > > only to discover when anaconda begins to install the packages that there > are some unsatisfied dependencies. > > I was just curious to see if anyone else is doing/has done this, and > whether they found a good way of checking the dependences of the packages > defined in the kickstart file prior to building the installation tree and > media, as this is takes quite a bit of time. > > Thanks very much, > Paul > > > -- > Paul Jefferson > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From mikolaj at kucharski.name Fri May 16 03:16:04 2014 From: mikolaj at kucharski.name (Mikolaj Kucharski) Date: Fri, 16 May 2014 04:16:04 +0100 Subject: How to use exising MD devices with anaconda 19.31.77-1 in RHEL7rc? Message-ID: <20140516031604.GL17403@openbsd-main.my.domain> Hi, I'm giving a spin RHEL7rc[1]. I had machine with 4 drives (2x3TB and 2x500GB), with following disk configuration: part raid.11 --size=512 --ondisk=sda --asprimary # /boot part raid.12 --size=2048 --ondisk=sda --asprimary # swap part raid.13 --size=2048 --ondisk=sda --asprimary # / part raid.15 --size=1 --grow --ondisk=sda # /var part raid.21 --size=512 --ondisk=sdb --asprimary # /boot part raid.22 --size=2048 --ondisk=sdb --asprimary # swap part raid.23 --size=2048 --ondisk=sdb --asprimary # / part raid.25 --size=1 --grow --ondisk=sdb # /var part raid.31 --size=512 --ondisk=sdc --asprimary # /boot part raid.32 --size=2048 --ondisk=sdc --asprimary # swap part raid.33 --size=2048 --ondisk=sdc --asprimary # / part raid.35 --size=1 --grow --ondisk=sdc # /var part raid.41 --size=512 --ondisk=sdd --asprimary # /boot part raid.42 --size=2048 --ondisk=sdd --asprimary # swap part raid.43 --size=2048 --ondisk=sdd --asprimary # / part raid.45 --size=1 --grow --ondisk=sdd # /var raid /boot --fstype ext4 --level=1 --device=md1 raid.11 raid.21 raid.31 raid.41 raid swap --fstype swap --level=10 --device=md2 raid.12 raid.22 raid.32 raid.42 raid / --fstype ext4 --level=10 --device=md3 raid.13 raid.23 raid.33 raid.43 raid pv.01 --level=1 --device=md8 raid.15 raid.35 raid pv.02 --level=1 --device=md9 raid.25 raid.45 volgroup vg0 pv.01 pv.02 logvol /var --fstype ext4 --vgname=vg0 --size=1 --grow --name=lv0 However one of the 500GB drives died and I'm waiting for replacement. All data is already wiped on existing drives, so I can do whatever I want on them. I would like to install RHEL7 before my replacement drive arrives, but I don't know how to specify `missing' (like in mdadm(8)) in Kickstart file, so I decided to create all partitions, MD and LVM volumes by hand: (drives have beginning and end of the drive wiped) parted -s /dev/sdX -- mklabel msdos # 500GB parted -s /dev/sdX -- mklabel gpt # 3TB Partitions created with parted as: mkpart primary 2048s 512MB # 512MB mkpart primary 512MB 2560MB # 2GB mkpart primary 2560MB 4608MB # 2GB mkpart primary 4608MB -1 # * MD devices created with: mdadm -C /dev/md1 -e default -n 4 -l raid1 /dev/sda1 /dev/sdb1 /dev/sdc1 missing mdadm -C /dev/md2 -e default -n 4 -l raid10 /dev/sda2 /dev/sdb2 /dev/sdc2 missing mdadm -C /dev/md3 -e default -n 4 -l raid10 /dev/sda3 /dev/sdb3 /dev/sdc3 missing mdadm -C /dev/md4 -e default -n 2 -l raid1 /dev/sda4 /dev/sdc4 mdadm -C /dev/md5 -e default -n 2 -l raid1 /dev/sdb4 missing Assembly devices with: mdadm -A /dev/md1 /dev/sda1 /dev/sdb1 /dev/sdc1 mdadm -A /dev/md2 /dev/sda2 /dev/sdb2 /dev/sdc2 mdadm -A /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdc3 mdadm -A /dev/md4 /dev/sda4 /dev/sdc4 mdadm -A /dev/md5 /dev/sdb4 Logical volume created as: pvcreate /dev/md4 /dev/md5 vgcreate vg0 /dev/md4 /dev/md5 vgchange -ay vg0 lvcreate -l 100%VG -n lv0 vg0 At this stage I have all devices needed to install the OS: /dev/md1 swap /dev/md2 / /dev/md3 /boot /dev/vg0/lv0 /var However when Anaconda starts, Dracut assebles the devices during %pre stage, I can start sshd via %pre script, I can login I can see volumes assembled (even if they wouldn't I can assembly them by hand in %pre), then Anaconda starts scaning storage devices, storage.log is filled with disocvered details and MD devices are all stopped (well, md4 and md5 fail to stop as they are busy, while being part of LVM) and installation fails with nonexsitent device md1. So, my question is, how to use exising partitions, to make Anaconda format them and install the OS? Actually, I can format them too, but how to make Anaconda keep going and insall everything. I've tried --onpart, --useexisting in so many different ways. I think I've tested all most obvious possible setups, but eatch time Anaconda stopped MD devices and Kickstart failed with nonexistent md device. Here are some examples: # fail, this doesn't work clearpart --none part /boot --fstype ext4 --onpart /dev/md1 part swap --fstype swap --onpart /dev/md2 part / --fstype ext4 --onpart /dev/md3 part /var --fstype ext4 --onpart /dev/vg0/lv0 # fail, this doesn't work clearpart --none raid /boot --fstype ext4 --useexisting --device=md1 raid swap --fstype swap --useexisting --device=md2 raid / --fstype ext4 --useexisting --device=md3 raid pv.01 --useexisting --device=md4 raid pv.02 --useexisting --device=md5 volgroup vg0 pv.01 pv.02 logvol /var --fstype ext4 --vgname=vg0 --size=1 --grow --name=lv0 Also, I don't exactly care how I can install RHEL7rc (as long as it's automatic, and I can repeat the step multiple times), but how to do it with missing drive, so when it arrices, I can just plug it in, partition it, re-install bootloader, and sync raid. [1]: http://ftp.redhat.com/redhat/rhel/rc/7/ -- best regards q# From mikolaj at kucharski.name Sat May 24 21:29:38 2014 From: mikolaj at kucharski.name (Mikolaj Kucharski) Date: Sat, 24 May 2014 22:29:38 +0100 Subject: How to use exising MD devices with anaconda 19.31.77-1 in RHEL7rc? In-Reply-To: <20140516031604.GL17403@openbsd-main.my.domain> References: <20140516031604.GL17403@openbsd-main.my.domain> Message-ID: <20140524212938.GW17403@openbsd-main.my.domain> It looks I'm affected by this: https://bugzilla.redhat.com/show_bug.cgi?id=1093144 -- best regards q# From mikolaj at kucharski.name Sat May 24 21:35:27 2014 From: mikolaj at kucharski.name (Mikolaj Kucharski) Date: Sat, 24 May 2014 22:35:27 +0100 Subject: How to use exising MD devices with anaconda 19.31.77-1 in RHEL7rc? In-Reply-To: <20140524212938.GW17403@openbsd-main.my.domain> References: <20140516031604.GL17403@openbsd-main.my.domain> <20140524212938.GW17403@openbsd-main.my.domain> Message-ID: <20140524213527.GX17403@openbsd-main.my.domain> On Sat, May 24, 2014 at 10:29:38PM +0100, Mikolaj Kucharski wrote: > It looks I'm affected by this: > > https://bugzilla.redhat.com/show_bug.cgi?id=1093144 Actually, I just realized I've lied. I got my replacement drive back and Kickstart failed with all 4 drives in it and with previously working configuration. That new failure is exacly like that from the Bugzilla. -- best regards q# From takamiya.noriaki at po.ntts.co.jp Fri May 30 06:05:34 2014 From: takamiya.noriaki at po.ntts.co.jp (Noriaki TAKAMIYA) Date: Fri, 30 May 2014 15:05:34 +0900 Subject: About NETWORK CONFIGURATION in kickstart process Message-ID: <53881FAE.5000705@po.ntts.co.jp> Hi, I'm new to anaconda, but I have one question. I'm going to install Fedora 20 with DVD media and kickstart file to PC which has no network interfaces. Everything is going well except that kickstart process stops at the NETWORK CONFIGURATION window with the message "We'll need network access to fetch information about your location and to make software updates available for you". Could you give me how to skip this NETWORK CONFIGURATION window? Regards, P.S. I attach using kickstart.cfg ----- #version=DEVEL # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Run the Setup Agent on first boot firstboot --enable # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' # System language # lang ja_JP.UTF-8 # Network information # network --hostname=localhost.localdomain #network --bootproto=static --device=lo --ip=127.0.0.1 --netmask==255.0.0.0 --nodefroute --nodns --hostname=localhost.lcoaldomain # Root password # # System timezone timezone --utc Asia/Tokyo # System bootloader configuration autopart --type=plain # Partition clearing information #clearpart --none --initlabel clearpart --all --drives=vda bootloader --location=mbr --boot-drive=vda ignoredisk --only-use=vda %packages @core %end -- NT -- users mailing list users at lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org From gnetravali at sonusnet.com Fri May 30 06:29:23 2014 From: gnetravali at sonusnet.com (Netravali, Ganesh) Date: Fri, 30 May 2014 06:29:23 +0000 Subject: About NETWORK CONFIGURATION in kickstart process In-Reply-To: <53881FAE.5000705@po.ntts.co.jp> References: <53881FAE.5000705@po.ntts.co.jp> Message-ID: <68B234C500D5C34EBCE58D977272260E528640@inba-mail01.sonusnet.com> Try below option to skip network config network --skip Ganesh -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Noriaki TAKAMIYA Sent: Friday, May 30, 2014 11:36 AM To: kickstart-list at redhat.com Subject: About NETWORK CONFIGURATION in kickstart process Hi, I'm new to anaconda, but I have one question. I'm going to install Fedora 20 with DVD media and kickstart file to PC which has no network interfaces. Everything is going well except that kickstart process stops at the NETWORK CONFIGURATION window with the message "We'll need network access to fetch information about your location and to make software updates available for you". Could you give me how to skip this NETWORK CONFIGURATION window? Regards, P.S. I attach using kickstart.cfg ----- #version=DEVEL # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Run the Setup Agent on first boot firstboot --enable # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' # System language # lang ja_JP.UTF-8 # Network information # network --hostname=localhost.localdomain #network --bootproto=static --device=lo --ip=127.0.0.1 --netmask==255.0.0.0 --nodefroute --nodns --hostname=localhost.lcoaldomain # Root password # # System timezone timezone --utc Asia/Tokyo # System bootloader configuration autopart --type=plain # Partition clearing information #clearpart --none --initlabel clearpart --all --drives=vda bootloader --location=mbr --boot-drive=vda ignoredisk --only-use=vda %packages @core %end -- NT -- users mailing list users at lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From takamiya.noriaki at po.ntts.co.jp Fri May 30 07:14:17 2014 From: takamiya.noriaki at po.ntts.co.jp (Noriaki TAKAMIYA) Date: Fri, 30 May 2014 16:14:17 +0900 Subject: About NETWORK CONFIGURATION in kickstart process In-Reply-To: <68B234C500D5C34EBCE58D977272260E528640@inba-mail01.sonusnet.com> References: <53881FAE.5000705@po.ntts.co.jp> <68B234C500D5C34EBCE58D977272260E528640@inba-mail01.sonusnet.com> Message-ID: <53882FC9.9070501@po.ntts.co.jp> Hi, (2014/05/30 15:29), Netravali, Ganesh wrote: > Try below option to skip network config > network --skip Thank you for yor reply. I added 'network --skip' line into my kickstart file, but the above options didn't work with Fedora20. Regards, -- NT From clumens at redhat.com Fri May 30 13:59:50 2014 From: clumens at redhat.com (Chris Lumens) Date: Fri, 30 May 2014 09:59:50 -0400 Subject: About NETWORK CONFIGURATION in kickstart process In-Reply-To: <53881FAE.5000705@po.ntts.co.jp> References: <53881FAE.5000705@po.ntts.co.jp> Message-ID: <20140530135950.GN7948@dhcp55.install.bos.redhat.com> > # Network information > # network --hostname=localhost.localdomain > #network --bootproto=static --device=lo --ip=127.0.0.1 > --netmask==255.0.0.0 --nodefroute --nodns --hostname=localhost.lcoaldomain The network line in your kickstart file is commented out. - Chris