#1035 F34: Ensure Fedora Cloud images get built in a legacy (BIOS) boot environment
Merged 2 years ago by mohanboddu. Opened 2 years ago by ngompa.
ngompa/pungi-fedora f34-fix-cloud-nightlies  into  f34

file modified
+2 -2
@@ -222,7 +222,7 @@ 

                      'release': None,

                      'ksurl': 'git+https://pagure.io/fedora-kickstarts.git?#origin/f34',

                      'kickstart': 'fedora-cloud-base.ks',

-                     'distro': 'Fedora-34',

+                     'distro': 'Fedora-22',

                      'disk_size': 4,

                      'arches': ['aarch64', 'ppc64le', 's390x', 'x86_64'],

                      'repo': [
@@ -242,7 +242,7 @@ 

                      'release': None,

                      'ksurl': 'git+https://pagure.io/fedora-kickstarts.git?#origin/f34',

                      'kickstart': 'fedora-cloud-base-vagrant.ks',

-                     'distro': 'Fedora-34',

+                     'distro': 'Fedora-22',

                      'disk_size': 40,

                      'arches': ['x86_64'],

                      'repo': [

The "Fedora-22" distro type configures the environment to use legacy (BIOS)
boot to setup the VM to build the image. This is required to ensure cloud
images are properly bootable.

Fixes: https://pagure.io/cloud-sig/issue/331

Pull-Request has been merged by mohanboddu

2 years ago
Metadata