Better log message in case even the first initialization didn't work
Bug #1169846 reported by
Didier Roche-Tolomelli
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
UTAH |
Fix Released
|
High
|
Javier Collado |
Bug Description
http://
The logs needs to explicitely say "initialization of hardware" or something like that to tell we are in the initialization steps and nothing occured yet.
Related branches
lp://qastaging/~javier.collado/utah/bug1169846
- Max Brustkern (community): Approve
- Diff: 0 lines
lp://qastaging/~javier.collado/utah/bug1169846-test-case
- Andy Doan (community): Approve
- Javier Collado (community): Needs Resubmitting
-
Diff: 70 lines (+37/-1)2 files modifiedtests/test_rsyslog.py (+36/-0)
utah/provisioning/rsyslog.py (+1/-1)
tags: | added: ue-desktop |
Changed in utah: | |
assignee: | nobody → Javier Collado (javier.collado) |
status: | New → Triaged |
importance: | Undecided → High |
Changed in utah: | |
status: | Triaged → In Progress |
status: | In Progress → Fix Committed |
Changed in utah: | |
status: | Fix Committed → Fix Released |
Changed in utah: | |
milestone: | none → 0.12 |
To post a comment you must log in.
Looking at the log, I see that a timeout for "system started".
The installation steps defined in the configuration file are:
- system started
- install started
- install complete.
I think that if the exception stated what are the remaining steps, that would
provide enough information for you to know what is missing. Do you agree on
that being a fix for the problem?