Bug 1506479

Summary: unable to boot into the former existing system after do another shrink installation
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: anaconda-maint-list, awilliam, jkonecny, jonathan, kellin, lnie, robatino, vanmeeuwen+fedora, vponcova, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: RejectedBlocker
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 19:51: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:
Description Flags
packaging.log none

Description lnie 2017-10-26 08:01:10 UTC
Created attachment 1343593 [details]

Description of problem:

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

How reproducible:

Steps to Reproduce:
1.Create a fresh VM with workstation-live using virt-manager
2.do a shrink installation with server-DVD
3.there is no workstation bootloader listed after you enable the boot menu

Actual results:

Expected results:

Additional info:

Comment 1 lnie 2017-10-26 08:01:52 UTC
Created attachment 1343594 [details]

Comment 2 lnie 2017-10-26 08:02:35 UTC
Created attachment 1343595 [details]

Comment 3 Fedora Blocker Bugs Application 2017-10-26 08:26:04 UTC
Proposed as a Blocker for 27-final by Fedora user lnie using the blocker tracking app because:

Looks like,but not sure,affects the final criteria:
Any installer mechanism for resizing storage volumes must correctly attempt the requested operation.

Comment 4 Adam Williamson 2017-10-26 16:21:13 UTC
I'm not sure we actually support dual-boot of two different installs of the same release of Fedora, which is really what you're talking about here. It's not a problem with shrinking, because it sounds like the shrinking part of the install worked fine. It's about dual-boot.

We in fact (still) don't have any 'dual-boot with Linux' criteria - we block on dual-boot with OS X and Windows, but not dual-boot with another Fedora install, or any other distro - so I'm -1 on this.

Comment 5 Adam Williamson 2017-10-26 20:04:06 UTC
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.

Comment 6 Jiri Konecny 2017-10-27 07:05:37 UTC
I guess you are experiencing the same issue as in the bug 1488204 .

Comment 7 Ben Cotton 2018-11-27 17:02:33 UTC
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.

Comment 8 Ben Cotton 2018-11-30 19:51:24 UTC
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

Thank you for reporting this bug and we are sorry it could not be fixed.