Bug 1000113

Summary: race condition during startup
Product: [Fedora] Fedora Reporter: David Shea <dshea>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, sbueno, stephent98, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-23 11:11:52 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
anaconda.log
none
traceback
none
anaconda-yum.conf
none
ifcfg.log
none
packaging.log
none
program.log
none
storage.log
none
storage.state
none
syslog
none
X.log none

Description David Shea 2013-08-22 13:46:49 EDT
Created attachment 789283 [details]
anaconda.log

Description of problem:
Crash during startup because some blivet calls that use g-i-introspection started before X did

Version-Release number of selected component (if applicable):
anaconda-19.30.13-1

How reproducible:
Obnoxiously rarely

Steps to Reproduce:
1. Started a virt-install using Fedora-19-x86_64-DVD.iso
2. Crash before the welcome screen.


Additional info:
In addition to the attached logs, the following was on tty1:

anaconda 19.30.13-1 for Fedora 19 started
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequenceLost' failed.
Comment 1 David Shea 2013-08-22 13:47:17 EDT
Created attachment 789284 [details]
traceback
Comment 2 David Shea 2013-08-22 13:47:46 EDT
Created attachment 789286 [details]
anaconda-yum.conf
Comment 3 David Shea 2013-08-22 13:48:14 EDT
Created attachment 789290 [details]
ifcfg.log
Comment 4 David Shea 2013-08-22 13:48:46 EDT
Created attachment 789291 [details]
packaging.log
Comment 5 David Shea 2013-08-22 13:49:12 EDT
Created attachment 789292 [details]
program.log
Comment 6 David Shea 2013-08-22 13:49:36 EDT
Created attachment 789294 [details]
storage.log
Comment 7 David Shea 2013-08-22 13:49:59 EDT
Created attachment 789295 [details]
storage.state
Comment 8 David Shea 2013-08-22 13:50:27 EDT
Created attachment 789296 [details]
syslog
Comment 9 David Shea 2013-08-22 13:50:56 EDT
Created attachment 789297 [details]
X.log
Comment 10 Steve Tyler 2013-08-22 16:58:33 EDT
The exception string is always the best choice for an initial bug summary:
AttributeError: 'NoneType' object has no attribute '__name__'

"race condition during startup" is your interpretation and not at all informative.
Comment 11 Steve Tyler 2013-08-22 17:04:56 EDT
It is also useful to paste error messages from the logs into a comment, so they can be found by searching BZ:

Error message from attached anaconda.log:
17:34:51,190 ERR anaconda: Problems running the window manager: [Errno 0] SIGCHLD caught when trying to start the X server.
Comment 12 Steve Tyler 2013-08-22 17:09:03 EDT
The log you have attached as "traceback" appears to be an anaconda-tb* file. Please use the exact name of the file, so that it can be recognized without opening it.
Comment 13 Steve Tyler 2013-08-22 17:13:17 EDT
(In reply to Steve Tyler from comment #12)
> The log you have attached as "traceback" appears to be an anaconda-tb* file.
> Please use the exact name of the file, so that it can be recognized without
> opening it.

This is the name you should use: "anaconda-tb-p_QLAy":
https://bugzilla.redhat.com/attachment.cgi?id=789284&action=edit

BTW, you can change it by clicking Details, Edit Details for the attachment.
Comment 14 Steve Tyler 2013-08-22 17:21:20 EDT
(In reply to Steve Tyler from comment #10)
> The exception string is always the best choice for an initial bug summary:
> AttributeError: 'NoneType' object has no attribute '__name__'
> 
> "race condition during startup" is your interpretation and not at all
> informative.

You can change the bug summary by clicking the "edit" link next to the bug summary at the top of the bug page.
Comment 15 Steve Tyler 2013-08-22 17:23:51 EDT
(In reply to David Shea from comment #0)
...
> How reproducible:
> Obnoxiously rarely
...

What is this supposed to mean?
Have you seen it more than once?
Comment 16 Chris Lumens 2013-08-23 09:51:42 EDT
Steve, please stop telling people who work on anaconda how to file and handle bugs in anaconda.  Your behavior is unhelpful and frankly quite rude.
Comment 17 David Shea 2013-08-23 09:54:21 EDT
Steve, traceback is just as descriptive as anaconda-tb-* as far as what's actually in the file. I really don't care what the output of mktemp was.

Yes, race condition is my interpretation.

It would be helpful if you would consolidate these comments into a single comment next time. Brevity is the soul of wit, but that doesn't count when multiplied by six.
Comment 18 Steve Tyler 2013-08-23 10:33:07 EDT
Chris, get out of your little I_Am_Anaconda world. Other people have to read bug reports to reproduce and analyze the bugs.

Dave, are your colleagues giving you any mentoring? Those faults in your bug report are so elementary, I was surprised to see an RH employee making them.

FYI, mktemp ensures uniqueness of names. When you are doing triage, maybe you have noticed that, sometimes, more than one anaconda-tb* file is attached. If everyone followed your one-name-fits-all approach, there could be several attachments, all named "traceback".

Also, you should state just the facts in your initial report and put your interpretation in followup comments. That way, the initial report is not biased by a possibly mistaken interpretation.

Here is some take-home reading:
Bug Writing Guidelines
https://bugzilla.redhat.com/page.cgi?id=bug-writing.html
Comment 19 David Cantrell 2013-08-23 11:11:52 EDT
This bug is being closed.  All further comments to it will be ignored.

Communication in this bug report is in violation of the Fedora Code of Conduct:

    http://fedoraproject.org/code-of-conduct