* Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)?
* Does the service listen on a network socket for connections originating on a separate physical or virtual machine?
* Is the service non-persistent (i.e. run once at startup and exit)?
* What is the exact name (or names) of the systemd unit files to be enabled?
* Is this request for all Fedora deliverables or only for some Editions (list them)?
(In reply to Bastien Nocera from comment #0)
> * Is the service non-persistent (i.e. run once at startup and exit)?
It is non-persistent, sorry
Ok, thanks. That meets the requirements to skip FESCo, so I will go ahead and merge it.
Note: I might need to get this reopened and reverted, if the patches in:
This needs to be reverted as it conflicts with https://github.com/rhinstaller/anaconda/pull/2039
There might be another way to solve this without reverting. I'll ask probinson what he thinks of this:
Longer explanation of the conflict:
This commit causes zram package's zram-swap.service to be enabled, and therefore creates swap on /dev/zram0 during early startup, including on LiveOS.
It hasn't landed in Rawhide yet, and even if it did the result is non-fatal.
What happens on LiveOS boots, is just some complaints from anaconda's own swap on zram (zram.service) trying to step on the zram0 device that this change creates during early boot (zram-swap.service).
If I simulate this commit by booting Fedora-Workstation-Live-x86_64-Rawhide-20190728.n.1.iso in a VM with `systemd.wants=zram-swap.service` and then launch Anaconda:
[root@localhost-live liveuser]# journalctl -b -o short-monotonic | grep zram
[ 91.209105] localhost-live zramswapon: + MAX_RAM_ON=2097152
[ 91.214632] localhost-live zramswapon: ++ grep MemTotal /proc/meminfo
[ 91.215386] localhost-live zramswapon: ++ grep -E --only-matching '[[:digit:]]+'
[ 91.224294] localhost-live zramswapon: + mem_total_kb=2008244
[ 91.224490] localhost-live zramswapon: + grep -E 'inst\.zram=(on|1)' /proc/cmdline
[ 91.229702] localhost-live zramswapon: + force=1
[ 91.230093] localhost-live zramswapon: + '[' '(' 2008244 -gt 2097152 ')' -a '(' 1 '!=' 0 ')' ']'
[ 91.231738] localhost-live zramswapon: ++ getconf _NPROCESSORS_ONLN
[ 91.244345] localhost-live zramswapon: + num_cpus=4
[ 91.244682] localhost-live zramswapon: + modprobe zram
[ 91.254963] localhost-live zramswapon: + echo 4
[ 91.256318] localhost-live zramswapon: + echo 2008244K
[ 91.264951] localhost-live kernel: zram: Cannot change disksize for initialized device
[ 91.257465] localhost-live zramswapon: /usr/libexec/anaconda/zramswapon: line 46: echo: write error: Device or resource busy
[ 91.257716] localhost-live zramswapon: + mkswap /dev/zram0
[ 91.280812] localhost-live zramswapon: mkswap: error: /dev/zram0 is mounted; will not make swapspace
[ 91.281568] localhost-live zramswapon: + swapon -p 100 /dev/zram0
[ 91.310634] localhost-live zramswapon: swapon: /dev/zram0: swapon failed: Device or resource busy
[ 91.312003] localhost-live zramswapon: + '[' 2008244 -le 1048576 ']'
[ 91.312431] localhost-live zramswapon: + exit 0
Basically, anaconda starts its own zram.service at launch (since a few Fedora releases on netinstalls, and starting with F31 for LiveOS which change just landed so there's no way bnocera could have known of the conflict) and because it's super simple, it just assumes it can setup swap on /dev/zram0, but there is already a swap setup there.
When I coordinated the change with anaconda folks, they wanted anaconda to start zram, because it's better for small RAM devices to fail during startup of the graphical environment, than for installation to succeed with zram, but then fail on reboot following installation because there was no zram.
Thing is, if we run into the problem that https://pagure.io/fedora-workstation/issue/98 is trying to solve, eventually the kernel is just going to spill over abruptly into that legacy swap on a conventional drive because the Anaconda creatd swap volume still exists along with this new swap on zram device.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 31 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.