Merge lp:~javier.collado/utah/bug1169846 into lp:utah

[Javier Collado]

The changes in this branch take care of displaying an error message that is
less confusing than the original one when there's a timeout for any of the
steps in the syslog messages. In particular, it adds what are the remaining
steps for the install to be successful. For example:
------------
UTAH timeout: Timeout (1) occurred for u'system started' message.
Remaining messages: install started, install complete
------------

Note that the exception type has been changed from UTAHException to UTAHTimeout
to take adavantage of the changes that have been comitted recently regarding
timeout exceptions.

What hasn't been updated are the steps names as has been discussed in the
launchpad bug. Anyway, now I think that it should be clearer that a timeout in
'system started' means that the installation didn't really start since 'install
started' is a remaining step.

[Max Brustkern (nuclearbob)]

This all looks good to me.

review: Approve

[lp:~javier.collado/utah/bug1169846]

875. By Javier Collado on 2013-04-19

Make rsyslog timeout error message clearer (LP: #1169846)

[Andy Doan (doanac)]

thanks for fixing the \n stuff in the exceptions. it was driving me nuts.

think you can come up with a test case for tests/test_rsyslog.py for this new change?

[Javier Collado (javier.collado)]

@Andy

I didn't see your comment before merging. Yes, I'll write such a test case and
create a new merge proposal.