jmccann, I saw this earlier today as well.  Can you take screenshots of the different tty's?  I believe tty3 or tty4 has an eject error on it?

Created attachment 366720 [details]
VT1

Created attachment 366721 [details]
VT3

That string comes from the livecd ks itself.  Warren has the info.

Discussed at today's blocker bug meeting, though we haven't made a discussion yet. Jesse summarizes the choices:

"so our options are A) try to fix plymouth so that we get our message, B) remove the messing with halt and regress 474817, C) do nothing and hope that the 30s timeout isn't too egregious"

Ray believes this change in initscripts may fix it:

ah ha
/etc/event.d/plymouth-shutdown doesn't have --attach-to-session
which means /dev/console messages aren't getting redirected
that may be why the message isn't showing up

Jesse is testing this theory at present. We'll continue to evaluate this one via this bug report.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Moving to plymouth according to that theory.

Note, plymouth-shutdown is in initscripts not plymouth (although maybe it should be in plymouth).

Anyway, this bug is sort of in my lap either way so assigning it to plymouth is fine.

well, the question is still whether we should attempt a fix for this bug in plymouth, try and work around it elsewhere, or leave it alone and document it...

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I think that we should probably revert the fix that was added in bug 474817 for a few reasons:

1) even if we fixed which vt the message was shown on, we'd only show the message for non-graphical users.  Graphical users would just get stuck wondering what's going on (or we would end up tearing down the graphical display and show text mode).

2) Warren says that he's run into issues where the eject happens too early sometimes and the system blows up (I don't know if he filed a bug for this or not)

3) the problem that's solved, only affects a subset of users with cd drives that can pull the cd back in, but the problem that's caused by the fix affects every user

4) we're getting down to the wire now.

For F13 i think we probably want better plymouth integration instead of 

echo blah > /dev/console

So the graphical case is right, and come up with a better implementation so that 2 doesn't happen.

(also for F13, we should fix plymouth so that /dev/console messages go to the right vt)

So after talking to Warren, I'm moving this to LiveCD.

> 3) the problem that's solved, only affects a subset of users with cd drives
> that can pull the cd back in, but the problem that's caused by the fix affects
> every user

This is a race condition where the device backing the root filesystem is disappearing and it subsequently tries to read from the block device to run the next command or read something necessary to proceed with shutdown.

I will figure out exactly which change this was and back it out.

The change was backed out in the config, closing this bug.