Bug 748811

Summary: Shutting down the installation: Assertion 'bus' failed at src/systemctl.c:1654, function start_special().
Product: [Fedora] Fedora Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-22 15:17:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 467765    
Attachments:
Description Flags
ps auxf none

Description Jan Stodola 2011-10-25 12:51:35 UTC 
Description of problem:
At the end of installation on s390x, anaconda doesn't shutdown system.
After clicking on Shutdown button, following message is displayed on terminal:

Assertion 'bus' failed at src/systemctl.c:1654, function start_special(). Aborting.
Connection to 10.16.105.198 closed.

But the system is still running - it means I can login via ssh.


Version-Release number of selected component (if applicable):
anaconda-16.22-1.fc16.dh.1
systemd-36-3.fc16.s390x

How reproducible:
always

Steps to Reproduce:
1. proceed through the installation process
2. at the finish screen, click on "Shutdown"
  
Actual results:
System doesn't shut down, assertion message on terminal

Expected results:
system should shut down (or reboot)
Comment 1 Chris Lumens 2011-10-29 15:20:44 UTC 
Is systemd running?
Comment 2 Jan Stodola 2011-10-31 09:43:13 UTC 
Created attachment 530932 [details]
ps auxf

Attaching list of processes before clicking on "Shutdown" button - systemd is not running.
Comment 3 Chris Lumens 2011-11-02 13:36:47 UTC 
This is because anaconda's using systemd on all platforms now except s390, where we're still using our own init.  However, we are universally trying to use systemctl to reboot the machine which of course won't work on a system where systemd isn't running.

A short term fix would be to modify the bottom of the anaconda script to do something different on s390.  I'd be happy to review patches that do that.  The real fix would be to ditch linuxrc.s390 and use loader and systemd like every other platform.
Comment 4 Chris Lumens 2012-10-22 14:59:32 UTC 
Are you still seeing this with F18?  There's no more linuxrc.s390, and a lot of work has gone into our systemd support.
Comment 5 Jan Stodola 2012-10-22 15:17:51 UTC 
I haven't seen this message for ages, so closing this bug as fixed.