Bug 1565694

Summary:	Anaconda installer does not allow start install if /bot is not on separate volume
Product:	[Fedora] Fedora	Reporter:	Tomasz Kłoczko <kloczko.tomasz>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	anaconda-maint-list, jonathan, kellin, sbueno, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 14:54:43 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:

Description Tomasz Kłoczko 2018-04-10 14:39:55 UTC

Latest grubby changes allows update boot menu if /boot is for example on btrfs.

Looks like anaconda still forces to install system with /boot on ext or xfs.

Comment 1 Samantha N. Bueno 2018-04-10 14:54:43 UTC


*** This bug has been marked as a duplicate of bug 1418336 ***