Local boot in uefi mode could not boot the user image(partition) when deployed with fedora deploy image

[vmud213]

When fedora distro is used as the deploy image, local boot in uefi mode could not boot the partition user image. Following is error is shown on the console:

No bootable devices were detected.
Please attach a UEFI bootable device.

For access via BIOS Serial Console:
Press 'ESC+9' for System Utilities
Press 'ESC+0' for Intelligent Provisioning
Press 'ESC+!' for One-Time Boot Menu
Press 'ESC+@' for Network Boot

System will automatically retry the UEFI Boot Order in 1 seconds.
>> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4)

>> Booting PXE over IPv4.
  PXE-E18: Server response timeout.
>> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv6)
>> Booting PXE over IPv6.
  PXE-E16: No offer received.

No bootable devices were detected.
Please attach a UEFI bootable device.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/302143

[Jay Faulkner (jason-oldos)]

How do we define a supported ramdisk? I question if an upstream bug in Fedora 22 should actually extend to being an IPA bug, especially when the fix is a distro-specific workaround.

[Jay Faulkner (jason-oldos)]

To be clear; I'm fully in support of supporting Fedora; just with it not being tested whatsoever today I'm not sure we should consider it supported. Additionally, IPA has no distro-specific code AFAIK and especially none for upstream bugs in distros (*inside IPA itself, not just in the ramdisk). This just seems like an infinite set of High bugs :)

[Julia Kreger (juliaashleykreger)]

The issue herew as actually ironic and the underlying support of UEFI boot mode. This has long since been added as a capability. As such updating this bug as appropriate.