Hide Forgot
Created attachment 1231444 [details] The anaconda logs when installation failed. Description of problem: 07:13:11,358 DEBUG anaconda: new disk order: [] 07:13:11,856 DEBUG anaconda: running handleException 07:13:11,856 CRIT anaconda: Traceback (most recent call last): File "/sbin/anaconda", line 1264, in <module> anaconda._intf.setup(ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/__init__.py", line 170, in setup should_schedule = obj.setup(self.ENVIRONMENT) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 62, in setup spoke.execute() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/spokes/storage.py", line 387, in execute doKickstartStorage(self.storage, self.data, self.instclass) File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 2061, in doKickstartStorage ksdata.partition.execute(storage, ksdata, instClass) File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1090, in execute doPartitioning(storage) File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 954, in doPartitioning allocatePartitions(storage, disks, partitions, free) File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 1309, in allocatePartitions _part.req_start_sector, _part.req_end_sector) File "/usr/lib/python2.7/site-packages/blivet/partitioning.py", line 790, in addPartition start = disklabel.alignment.alignNearest(free, start) File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 41, in new ret = fn(*args, **kwds) File "/usr/lib64/python2.7/site-packages/parted/alignment.py", line 102, in alignNearest return self.__alignment.align_nearest(geom.getPedGeometry(), sector) ArithmeticError: Could not align to closest sector Version-Release number of selected component (if applicable): How reproducible: Install the system through PXE+kickstart Actual results: Failed to complete the hard disk partition, the installation fails. Expected results: System installation can complete. Additional info:
Created attachment 1231445 [details] The storage logs when installation failed.
Created attachment 1231446 [details] The kickstart configuration file
There is reason to believe this is fixed in RHEL-7.3. At the very least the behavior should be different there. Can the customer try the installation using that and report the outcome?