Created attachment 1343610 [details] journal from the workstation system Description of problem: Please see the reproducer,thanks. The server system's network is fine,but the workstation's is not. Not sure this is the right place for the report,please fee free to reassign,thanks. Version-Release number of selected component (if applicable): Fedora-Server-dvd-x86_64-27-20171023.n.0.iso Fedora-Workstation-Live-x86_64-27-20171023.n.0.iso How reproducible: always Steps to Reproduce: 1.create a fresh VM with dvd-server image using virt-manager,and leave enough free space for another installation 2.do another installation with workstation-live image 3. Actual results: Expected results: Additional info:
I was wrong,workstation will be out of network,no matter it's the first or second installed,while server system's network is always fine. It's likely that if you install workstation after server installation,its network is fine on the first boot,but after you boot the server system,the workstation one will be out of network ever sine.
Created attachment 1343653 [details] anaconda.log when the workstation is second insatlled
Created attachment 1343654 [details] storage.log when the workstation is second insatlled
Created attachment 1343655 [details] anaconda.log when the workstation is first insatlled
Created attachment 1343656 [details] storage.log when the workstation is first insatlled
Proposed as a Blocker for 27-final by Fedora user lnie using the blocker tracking app because: Looks like,but really not sure,affects the criteria: All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present.
again I'm -1 because this kind of 'two installs of the same release on the same system' scenario isn't one we really cover. I suspect it'd behave much the same way if you tried with 25 or 26?
Discussed at 2017-10-26 Fedora 27 Final go/no-go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-10-26/f27-final-and-server-beta-go-no-go-meeting.2017-10-26-17.00.html . Rejected as a blocker on the basis that the criteria do not cover this kind of "dual-boot the same Fedora release" scenario.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.