Bug 1400473

Summary: kickstart: creating a volgroup with default physical extent fails in i686 architecture under VirtualBox
Product: [Fedora] Fedora Reporter: Enrique <cquike>
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: 24CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, vanmeeuwen+fedora, vponcova
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: 2017-08-08 19:23:30 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 Flags
Fedora 24 i686 Kickstart that fails at logvol command none

Description Enrique 2016-12-01 10:19:17 UTC
Created attachment 1226729 [details]
Fedora 24 i686 Kickstart that fails at logvol command

Description of problem:

 I have tried to install Fedora 32 bits via kickstart in a virtual machine using VirtualBox but the installation complains a a problem with the kickstart file:

"storage configuration failed The following problem occurred on line 18 of the kickstart file:

Volume group given physical extent size of "4 MiB", but must be one of:
1 KiB."

 The kickstart file looks like this around line 18:

15 clearpart --all --initlabel
16 #Manual partition
17 part pv.01 --grow
18 volgroup fedora pv.01
19 logvol / --vgname=fedora --size=1 --grow --name=root
20 logvol swap --vgname=fedora --recommended  --name=swap


Version-Release number of selected component (if applicable):
 
 Fedora 24 with ISO Fedora-Server-netinst-i386-24-1.2.iso

 I have selected some of the the VM configuration within VirtualBox that looks relevant to me:

 General -> basic -> Type: Linux
 General -> basic -> Version: Fedora (32 bits)
 System -> Motherboard -> Chipset -> PIIX3
 System -> Motherboard -> Enable I/O APIC -> NOT set
 Storage -> Controller: SATA Controller -> fedora-24-i386.vdi -> Type -> Normal (VDI)
 

How reproducible:

 Always

Comment 1 Enrique 2016-12-01 10:20:13 UTC
 By the way: the same kikcstart works fine installing a x86_64 guest.

Comment 2 Fedora End Of Life 2017-07-26 00:02:03 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 3 Fedora End Of Life 2017-08-08 19:23:30 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.