| Summary: | Install fails with no obvious reason | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexander Todorov <atodorov> | ||||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||
| Priority: | high | ||||||||||||||||
| Version: | 20 | CC: | anaconda-maint-list, atodorov, dshea, g.kaviyarasu, jonathan, mkolman, rjones, sbueno, stephent98, vanmeeuwen+fedora, vpodzime | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | 1003106 | Environment: | |||||||||||||||
| Last Closed: | 2014-02-25 22:56:24 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Alexander Todorov
2013-09-24 06:20:20 UTC
Created attachment 802054 [details]
anaconda.log
Created attachment 802055 [details]
console.log
Created attachment 802056 [details]
program.log
Created attachment 802057 [details]
storage.log
Created attachment 802058 [details]
sys.log
Created attachment 802059 [details]
vncserver.log
What do you think by "Install fails"? What happens and in which step/phase does it happen? From the logs it seems it's at some point after the first screen. Well if I knew what happened I would have told you. These are automated test jobs I don't monitor them during install, I just saw it aborted, while install (it looks like so). I see couple of GTK errors but they are not critical. The one that looks suspicious is the last one: (anaconda:864): Gdk-CRITICAL **: gdk_window_move_resize_internal: assertion 'GDK_IS_WINDOW (window)' failed You have all the logs. I expect you to make sense of them more than I do. I think there were exceptions happening in the installation (most probably the "YumBase object has no attribute _preconf" one). None of the logs shows anything like "fail for no obvious reason". Unless you can reproduce this in an "non-unattended" installation and provide some more information about what happened, I'm gonna close this as CANTFIX. |