rhinstaller / fedup-dracut Goto Github PK

If we can't do graphical boot, the text "progress bar" doesn't really give any idea what's going on. Should switch to details mode so the user can see progress being made.

see e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1017201

fedup-dracut $ sudo make repo
mkdir repo
./makefeduprepo repo || rm -rf repo
creating fedup-capable repo at repo

• copying kernel to vmlinuz
• building upgrade.img (this will take a moment..)
  E: dracut module 'plymouth-label' cannot be found or installed.
  E: dracut module 'plymouth-label' cannot be found or installed.
  I: *** Including module: i18n ***
  I: *** Including module: network ***
  I: *** Including module: ifcfg ***
  I: *** Including module: drm ***
  I: *** Including module: plymouth ***
  modifying plymouthd.conf: Theme=fedup
  I: *** Including module: system-upgrade-fedora ***
  I: *** Including module: btrfs ***
  I: *** Including module: crypt ***
  I: *** Including module: dm ***
  I: Skipping udev rule: 64-device-mapper.rules
  I: *** Including module: dmraid ***
  I: *** Including module: kernel-modules ***
  I: Omitting driver nfs_acl
  I: Omitting driver nfs
  I: Omitting driver nfsv2
  I: Omitting driver nfsv3
  I: Omitting driver nfsv4
  I: Omitting driver nfs_layout_nfsv41_files
  I: Omitting driver objlayoutdriver
  I: Omitting driver blocklayoutdriver
  I: Omitting driver nfsd
  I: Omitting driver lockd
  I: *** Including module: lvm ***
  I: Skipping udev rule: 64-device-mapper.rules
  I: *** Including module: mdraid ***
  I: *** Including module: multipath ***
  I: Skipping udev rule: 40-multipath.rules
  I: *** Including module: cifs ***
  I: *** Including module: fcoe ***
  I: *** Including module: iscsi ***
  I: *** Including module: nfs ***
  I: *** Including module: resume ***
  I: *** Including module: rootfs-block ***
  I: *** Including module: terminfo ***
  I: *** Including module: udev-rules ***
  I: *** Including module: biosdevname ***
  I: *** Including module: systemd ***
  I: *** Including module: usrmount ***
  I: *** Including module: base ***
  I: *** Including module: fs-lib ***
  I: *** Including module: shutdown ***
  I: *** Including modules done ***
  I: *** Installing kernel module dependencies and firmware ***
  I: *** Installing kernel module dependencies and firmware done ***
  I: ** Resolving executable dependencies ***
  I: * Resolving executable dependencies done
  I: *** Hardlinking files ***
  I: *** Hardlinking files done ***
  I: *** Stripping files ***
  I: *** Stripping files done ***
  I: *** Creating image file ***
  I: *** Creating image file done ***
  I: Wrote /home/saga/fedup-dracut/repo/upgrade.img:
  I: -rw-------. 1 root root 42567346 Nov 18 17:16 /home/saga/fedup-dracut/repo/upgrade.img
• writing .treeinfo
• creating repodata
  done.

It turns out that loading policy in initramfs is a Bad Idea, for reasons that are complicated and weird. This is the root cause of the multiple-LUKS-partition bug, among other things.

After some discussion on the SELinux mailing list, we came to the conclusion that the Right Thing To Do is to let the old system load its policy, then load new policy when we switch back into upgrade.img.

To do that, we need systemd to load policy more than once, which it currently doesn't. This patch fixes that, but it hasn't been committed yet.

Once it is committed, we should:

• make fedup-dracut not load SELinux policy during initramfs, and
• make sure policy gets reloaded after the switch-root back to fedup-dracut

The last package to be installed will have a message like:

[1273/1272] (72%) installing ...

This is pretty minor but it should be easy to fix or ignore.

This might actually be a bug / confusing behavior in the RPM library itself?