Bug 886033

Problem Description
--------------------------
Installation fails on EDEV (Emulated FBA) device
 
---uname output---
3.3.0-0.20.el7
 
Machine Type = 2817 

Steps to Reproduce
---------------------------
1. Apply the parted patches from LTC bug # 84317 and 84318

Bug 84318 - RH707032- Installation on EAV DASD failed
Bug 84317 - RH707027 - RFE: Installation on Z/VM EDEV failed during format

2. Try installing on EDEV device. Installation fails.

3. Some of the functions from 'parted' are required to be available for Anaconda to exploit the changes done for EAV/EDEV devices. So changes are required for 'pyparted'.

== Comment: #3 - NAGESWARA R. SASTRY <nasastry.com> - 2012-12-07 05:48:48 ==
1. What is EDEV device:
Fixed Block Access (FBA) DASDs are mainframe-specific disk devices
which are layed out as a sequence of 512-byte sectors. In contrast
to ECKD DASDs, these disks do not require formatting and resemble
the LBA layout of non-mainframe disks. Despite this resemblance,
the Linux kernel applies special handling during partition detection
for FBA DASDs, resulting in a single, immutable partition being
reported.

While actual FBA DASD hardware is no longer available, the z/VM
hypervisor can simulate FBA DASD disks, backed by either ECKD or
SCSI devices.

2. How does installation fail
The function 'ped_disk_new_fresh' exported to Anaconda as
'freshPartedDisk', which set the type of the disk to a device.
This function sets wrong meta-data to EDEV disk.

3. Why does it fail
Because of the wrong meta-data on EDEV devices.

4. How does this patch solve this problem.
The proper meta-data written to the EDEV kind of disks by function
named 'ped_disk_new'. So this function is exported to Anaconda as
'newPartedDisk'. This will help in writing correct meta-data to the
disk. Having correct meta-data on the disk will help in successful
installation.