Bug 947031
| Summary: | Can not connect to network - bridge in kvm | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tao Wu <twu> | ||||||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 19 | CC: | g.kaviyarasu, jonathan, mkolman, sbueno, sdharane, 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: | 2015-02-17 14:55:23 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: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Please attach these log files: /tmp/anaconda.log /tmp/syslog /tmp/ifcfg.log as individual text/plain attachments. As the network is not connected in your case, you'll probably need to copy them to some storage mounted from tty2. Created attachment 731067 [details]
anaconda log
Created attachment 731068 [details]
syslog
Created attachment 731069 [details]
ifcfg log
(In reply to comment #1) > Please attach these log files: > /tmp/anaconda.log > /tmp/syslog > /tmp/ifcfg.log > as individual text/plain attachments. > As the network is not connected in your case, you'll probably need to copy > them to some storage mounted from tty2. Hi Radek, I have uploaded these log files, thanks! Looking at the log files the installer is connected to the network (ens3 is activated) which does not correspond to screenshot from the Description. Either the UI is lying (which would be a bug) or the logs come from another (working) instance of installation. Looks strange to me. This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 730216 [details] screenshot Description of problem: F19 alpha TC3 i386 DVD can not connect to network in kvm, and the network method is bridge. Version-Release number of selected component (if applicable): 19.14 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: