Anaconda-devel July 2020

anaconda-devel@lists.stg.fedoraproject.org

9 participants
6 discussions

Should pykickstart sort Packages.packageList and .excludedList?
by Brian C. Lane 30 Jul '20

30 Jul '20

We're trying to reduce the number of external modules we depend on, and the subject of the OrderedSet modules came up. I've put together a PR here - https://github.com/pykickstart/pykickstart/pull/325 I wasn't able to figure out exactly why we switched to using OrderedSet, the commit wasn't clear as to why it was needed. Internal to the add() function I can see no reason for it, the add and exclude lists are independent of each other so the ordering shouldn't matter when doing the set operations. The only thing I can think of is dnf, via anaconda, and it really shouldn't care either. So I dropped it, turning it back into a regular set, and I just sort the results when storing them so that they'll always have a consistent order. Does this look ok to everyone? Can anyone think of a reason not to do this? Have I missed something obvious here? :) Please comment on the PR so the discussion can all be in one place. Thanks, Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart

1 0

Booting from isolinux's vmlinuz and initrd.img
by Prarit Bhargava 27 Jul '20

27 Jul '20

Hey everyone, I have a Fedora question but really an overall RH OS question: I am running Fedora 32 on x86_64. I used to be able to boot into the installer using the vmlinuz and initrd.img from the isolinux directory. IIRC I had to specify a boot entry like title loader linux /vmlinuz inst.vnc initrd /initrd.img grub_users $grub_users grub_arg --unrestricted grub_class kernel but that no longer seems to work and I see a hang during systemd. I do see that the bootlog has [ 26.758433] dracut-cmdline[1226]: Warning: anaconda requiring network for vnc so I know I'm on the right track. Does anyone know the magic incantation to get this to work? I have a remote system I'm trying to install. TIA for any help, P. P.S the hang occurs here: [ OK ] Started cancel waiting for multipath siblings of sda. [ OK 46.572336] audit: type=1130 audit(1594832545.563:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udev-settle comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 0m] Finished udev Wait [ 46.598261] audit: type=1130 audit(1594832545.589:12): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=multipathd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' for Complete Device Initialization. Starting Device-Mapper Multipath Device Controller... [[ 46.632797] audit: type=1130 audit(1594832545.623:13): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=iscsid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' OK ] Started Dev[ 46.656741] audit: type=1130 audit(1594832545.647:14): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ice-Mapper Multipath Device Controller. [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting Open-[ 46.702841] audit: type=1334 audit(1594832545.693:15): prog-id=5 op=UNLOAD [ 46.711037] audit: type=1334 audit(1594832545.693:16): prog-id=4 op=UNLOAD [ 46.718725] audit: type=1334 audit(1594832545.693:17): prog-id=3 op=UNLOAD [ 46.726410] audit: type=1334 audit(1594832545.694:18): prog-id=7 op=UNLOAD [ 46.734090] audit: type=1334 audit(1594832545.717:19): prog-id=6 op=UNLOAD iSCSI... Starting Create Volatile Files and Directories... [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ OK ] Finished Create Volatile Files and Directories. [ OK ] Reached target System Initialization. [ OK ] Reached target Basic System. [ 46.813521] audit: type=1334 audit(1594832545.804:20): prog-id=8 op=LOAD [ 47.204855] pps pps0: new PPS source ptp0 [ 47.209461] ixgbe 0000:03:00.0: registered PHC device on ens1f0 [ 47.354545] 8021q: adding VLAN 0 to HW filter on device ens1f0 [ 47.635054] pps pps1: new PPS source ptp1 [ 47.639661] ixgbe 0000:03:00.1: registered PHC device on ens1f1 [ 47.785159] 8021q: adding VLAN 0 to HW filter on device ens1f1 [ 50.593094] ixgbe 0000:03:00.0 ens1f0: NIC Link is Up 1 Gbps, Flow Control: None [ 50.601652] IPv6: ADDRCONF(NETDEV_CHANGE): ens1f0: link becomes ready [ 51.093012] ixgbe 0000:03:00.1 ens1f1: NIC Link is Up 1 Gbps, Flow Control: None [ 51.101559] IPv6: ADDRCONF(NETDEV_CHANGE): ens1f1: link becomes ready [ OK 57.190473] kauditd_printk_skb: 4 callbacks suppressed [ 57.190476] audit: type=1130 audit(1594832556.181:25): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=cancel-multipath-wait-sda comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 57.220872] audit: type=1131 audit(1594832556.204:26): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=cancel-multipath-wait-sda comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 0m] Started cancel waiting for multipath siblings of sda. [ 227.583366] dracut-initqueue[2227]: Warning: dracut-initqueue timeout - starting timeout scripts [ 228.322868] dracut-initqueue[2227]: Warning: dracut-initqueue timeout - starting timeout scripts [ 229.045556] dracut-initqueue[2227]: Warning: dracut-initqueue timeout - starting timeout scripts

2 1

F33: preview swap-on-ZRAM using zram-generator feature change
by Chris Murphy 16 Jul '20

16 Jul '20

Hi, I'm following-up now that there's a preview of the change proposal ready: https://fedoraproject.org/wiki/Changes/SwapOnZRAM Highlights: - This is a system-wide change, for all editions and spins. And if Anaconda folks are still agreeable, it would be included on all install media where Anaconda is found: DVD/Live/netinstall. - Fedora Workstation edition will no longer create swap-on-disk by default. Instead swap-on-zram will be used. I expect to get buy-in from other editions/spins to do the same. This applies only to the default/automatic partitioning path, as previously discussed. - Tentative (proposed) defaults similar to what's used by IoT: ZRAM device is 50% RAM, with a 4GiB cap. The max size, which is configurable, is to help scale ZRAM device size for more uses cases and hopefully settle on a single default Fedora wide. This is a bit different than Anaconda's implementation, which doesn't activate above 2GiB, and uses a 1:1 ZRAM to RAM ratio. Based on my testing, even VM's with 3GiB RAM still prefer to use quite a decent amount of swap ~200MiB. If it's available. I think this adjustment is neutral to slightly better for Anaconda. And in any case the installer and installed environments will have the same configuration and implementation as a result of the change. - Disable or somehow deprecate the Anaconda specific implementation, to avoid conflict and user confusion among the implementations. - Test day will be planned Critical feedback welcome. -- Chris Murphy

6 24

Question about initramfs differences in RHEL7 and RHEL8
by Mohammed Gamal 14 Jul '20

14 Jul '20

Hi, We're having this issue where we see different behavior on KVM guest images between RHEL7 and RHEL8. See this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1852761 What's happening is that the initramfs in RHEL7 contains the Xen drivers required for running these images on EC2 instances (and more than 600 drivers), while the initramfs in RHEL8 doesn't contain these drivers (it contains only 177 drivers), strangely enough the upcoming RHEL8.3 images seem to contain these drivers (and again much more than just 177 drivers). The kickstart files in all these cases don't explicitly call dracut to add these drivers. I am suspecting it might be the way anaconda calls dracut to generate the initramfs might've changed between RHEL7 and RHEL8 and that caused this change in behaviour. Any ideas where to look? Thanks, Mohammed

1 0

Making anaconda disable some storage-related systemd services in post-install config part of livecd install?
by Hans de Goede 09 Jul '20

09 Jul '20

Hi All, For those of you who are still around from when I was a part of the anaconda team: long time no see. First some background on $subject: The Fedora workstation livecd is the default Fedora variant getfedora.org advices people to download. As such most Fedora workstation installs will be done from the livecd. As you very well know, with livecd installs the packageset installed is the one which used to compose the livecd, since the rootfs is simply rsync-ed over. This means that any storage related packages which may be necessary in some exotic setups are part of the livecd. Some of these storage related packages are poorly behaved wrt their systemd services, they come with services which simply always run. 2 of these are particularly bad because they also bring in (through Requires=) the long obsolete systemd-udev-settle service significantly delaying the boot. These are dmraid and device-mapper-multipath. As you may have seen I have proposed 2 changes for Fedora 33 to deal with this: https://fedoraproject.org/wiki/Changes/DisableDmraidOnFirstRun https://fedoraproject.org/wiki/Changes/RemoveDeviceMapperMultipathFromWorks… These are currently being discussed on the fedora-devel mailinglist. One suggestion which came up there and which I think is probably a better idea then my original solutions is to make anaconda disable the related services in the post-install config part of the livecd install. This should be easy to implement, unless this has changed since I last worked on anaconda, the storage code will provide a list of extra packages which need to be installed because they are necessary for the chosen storage config. My idea is to have a table (somewhere) with mappings of storage packages to service-names to disable. Then the livecd post-install config code can ask the storage code for the list of necessary packages and then walk over this new table. If a package is not listed as being necessary by the storage code, then the livecd post-install config code can run "systemctl disable $mapped-service.service" thus disabling any (bad behaved) storage services which are not necessary. For starters this table would just contain dmraid and device-mapper-multipath, but I think this would be a nice generic config mechanism which we might be able to use for some other cases in the future. So 2 questions: 1. What do you think of my proposal to disable these services (when not needed) in the livecd post-install config phase? Would you be willing to accept a merge-req for this? 2. Its been a long time since I last touched the anaconda code, my python is quite rusty and my plate is way too full, so I was wondering if one of you could implement this if we chose to go this route? Regards, Hans

6 14

sd-boot for UEFI installs
by Jóhann B. Guðmundsson 01 Jul '20

01 Jul '20

Hi I'm looking into the scope of replacing grub2 with sd-boot for UEFI installs in Fedora and I'm wondering how such a change would affect Anaconda and if Anaconda is capable of detecting if legacy bios settings is in use and if so install and setup grub2 and if not install and setup sd-boot. Thanks JBG

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel July 2020