I downloaded the Fedora 33 Sugar-on-a-stick GA ISO from the link on the getfedora.org website:
When I boot that in a KVM VM it boots but it does not autologin. It gives a graphical login manager screen and other is selected. Trying to use liveuser without a password doesn't work. Switching over to a text-based console and trying to login as liveuser or root (both without passwords) doesn't work.
So far as I can tell, the media is broken and shouldn't have been released.
Another user in the #fedora channel on IRC said they were able to verify the issue too.
I see this issue with Fedora-SoaS-Live-x86_64-33-1.2.iso
So I happened to debug this issue out of curiosity by using systemd debug shell, i.e.
- adding "systemd.debug-shell=1 systemd.log_level=debug"
- switch to ctrl-alt-F9
- debug what is happening
* Looking at /etc/passwd, "liveuser" user is *not* created
* Looking at /etc/shadow, root password is *locked*
* Looking at /var/log/boot.log , there is no message for "Starting LSB: Init script for live image..."
So when booting Fedora-SoaS-Live-x86_64-33-1.2, it seems /etc/rc.d/init.d/livesys script was never executed.
Actually executing this script manually (in systemd debug shell) fixes this issue.
So my guess is:
- Some file is missing which prevents systemd from executing systemd-sysv-generator
- Something is wrong in /etc/rc.d/init.d/livesys (in Soas live image) and systemd cannot determine order
dependency or so
Try the refreshed SoaS media created by the Respin SIG. I believe it is working as desired.
I don't know the detail of systemd, however I guess what is actually needed is /usr/lib/systemd/systemd-sysv-install
( which is symlink to /sbin/chkconfig ).
This is in chkconfig-1.14-3.fc33 , which is actually installed in LXDE Fedora 33 live (I am LXDE live maintainer),
but actually chkconfig is *not installed* in Fedora-SoaS-Live-x86_64-33-1.2.iso .
Fedora-SoaS-Live-33-20201023.n.0 is not exactly the same as Fedora-SoaS-Live-x86_64-33-1.2.iso, however looking
at koji log:
10:58:48,278 DBG packaging: transaction exclude list
10:58:48,278 DBG packaging: ['@dial-up', '@fonts', '@gnome-desktop', '@multimedia', '@printing', 'PackageKit', 'abrt-cli', 'chkconfig', 'device-mapper-multipath', 'dhcp-client', 'eekboard-libs', 'fcoe-utils', 'firefox', 'foomatic', 'gcc', 'gcc-gdb-plugin', 'gfs2-utils', 'glx-utils', 'hplip', 'hyperv-daemons', 'ibus*', 'icedtea-web', 'isdn4k-utils', 'mpage', 'nmap-ncat', 'open-vm-tools*', 'openbox', 'plymouth-system-theme', 'plymouth-theme-charge', 'rdate', 'rdist', 'sane-backends', 'sane-backends-drivers-scanners', 'xsane', 'xsane-gimp', 'yp-tools', 'ypbind']
...... Okay, actually there is https://pagure.io/fedora-kickstarts/c/d8d2e8e2d8535eae3dd841339dbe306a2f6b1fcb?branch=f33 ,
perhaps this is the culprit.
(In reply to Mamoru TASAKA from comment #3)
> I don't know the detail of systemd, however I guess what is actually needed
> is /usr/lib/systemd/systemd-sysv-install
> ( which is symlink to /sbin/chkconfig).
Why is it still using sys-v scripts?
> This is in chkconfig-1.14-3.fc33 , which is actually installed in LXDE
> Fedora 33 live (I am LXDE live maintainer),
> but actually chkconfig is *not installed* in
> Fedora-SoaS-Live-x86_64-33-1.2.iso .
Why should it be, we dropped SYS-V scripts in like Fedora 22, it should have *LONG* been converted to a proper systemd script and not depend on legacy deprecated things.
(In reply to Peter Robinson from comment #4)
> (In reply to Mamoru TASAKA from comment #3)
> > I don't know the detail of systemd, however I guess what is actually needed
> > is /usr/lib/systemd/systemd-sysv-install
> > ( which is symlink to /sbin/chkconfig).
> Why is it still using sys-v scripts?
> > This is in chkconfig-1.14-3.fc33 , which is actually installed in LXDE
> > Fedora 33 live (I am LXDE live maintainer),
> > but actually chkconfig is *not installed* in
> > Fedora-SoaS-Live-x86_64-33-1.2.iso .
> Why should it be, we dropped SYS-V scripts in like Fedora 22, it should have
> *LONG* been converted to a proper systemd script and not depend on legacy
> deprecated things.
Just look at:
Note that here we are talking about livespin, not installed image. livespin creates
"liveuser" user, which is (currently) done by this sysv script.
peter: I rewrote the on-the-fly live initscripts as systemd services years ago but it sat around because Bruno didn't think it was an improvement:
I've never felt like re-doing it, and I don't think anyone else has either. So they're still initscripts.
Related to this was a long-ago-closed will-not-fix RFE... requesting the removal of the livesys services at first boot of the installed system since they are no longer needed... but it was closed because keeping them there was thought not to have a negative impact as they don't do anything other than get parsed. While it might not have a noticeable performance impact... it does often lead to questions from users about why those services are there, what they are for... and can they be turned off. They really should go away post install.
So if anyone works on a fix for this ticket and in involves converting the services to systemd or whatever, please consider adding auto-removal post-install as well to the update... if it isn't too much additional work.
This bug still there.
I tried the last respin, from 2021-01-29 and it starts normaly, without any bugs ( https://dl.fedoraproject.org/pub/alt/live-respins/F33-SOAS-x86_64-LIVE-20210129.iso )
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
(In reply to Geraldo Simião from comment #10)
> I tried the last respin, from 2021-01-29 and it starts normaly, without any
> bugs (
> 20210129.iso )
Thank you for the report. This undesirable behavior is also present in the Fedora 34 nightly, and I'm not sure why. Peter, any thoughts on why it works on the F33 respin, but not F34?
The latest respin is now from 2021-0212 and also starts normally!
This build from F34 is working fine, no bugs.
I have just signed up to requesting this be reopened. I am getting the same issue on F35 SoaS. Since I also cannot find download links to previous versions, there seems to be no way for me to install this operating system. Presumably I am not the only one?
This is not likely the same problem, because according to comments 13 and 14, F34 was OK. So ccansomeone please just file a *fresh* bug for F35 describing the problems there anew? Thanks. I also asked this on https://bugzilla.redhat.com/show_bug.cgi?id=2035970 , so we just need *one* new bug.