From Fedora Project Wiki
No edit summary
Line 26: Line 26:
* Release-blocking cloud images must allow login with the user authentication configuration requested during instance creation.
* Release-blocking cloud images must allow login with the user authentication configuration requested during instance creation.
* Release blocking IoT images must boot and be configurable by the Zezere utility.
* Release blocking IoT images must boot and be configurable by the Zezere utility.
* Release blocking FCOS images must boot and install following the coreos-installer workflow
* ''Release blocking FCOS images must boot and install following the coreos-installer workflow'''''NEW'''
{{hidden|header=Boot menu contents|content=The boot menu for all supported installer and live images should include an entry which causes both installation and the installed system to attempt to use a generic, highly compatible video driver (such as 'vesa').|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
 
{{hidden|header=System-specific bugs|content=System-specific bugs don't necessarily constitute an infringement of this criterion - for instance, if the installer or desktop fails to start because of a bug in support for some specific graphics card, that is unlikely to constitute a violation. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
==== Remote package sources ====
{{hidden|header=References|content=
When using a release-blocking dedicated installer image, the installer must be able to use HTTP and HTTPS repositories as package sources. Release-blocking network install images must default to a valid publicly-accessible package source.
* [[rhbug:614488|Bugzilla: #614488]] was proposed as Alpha blocker for F14. Bug was fixed before before blocker status was confirmed or rejected.
{{hidden|header=FCOS remote repos|content=
* Proposed [https://lists.fedoraproject.org/pipermail/test/2010-July/092148.html 2010-07-16].
In FCOS, coreos-installer should be able to fetch a remote "rootfs" if needed.
* Implemented [https://lists.fedoraproject.org/pipermail/test/2010-July/092231.html 2010-07-23].
* Rewritten as part of major Fedora 19 criteria revision.
* 'Basic graphics' mode portion split between Beta and Final [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/6QZAKQI3MYMVF5RPUJDRZGQC6LWK2GLM/ 2019-04-02]
* Test cases: see test cases for [[#release-blocking-images-must-boot|"Release-blocking images must boot"]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}


{{anchor|installer-requirements}}




==== Release-blocking images must boot ====
All release-blocking images must boot in their supported configurations.
{{hidden|header=Supported architectures|content=Supported architectures are the Fedora [[Architectures#Primary_Architectures|primary architectures]]. All images are not necessarily expected to be available for all primary architectures.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported firmware types|content=Release-blocking images must boot from all system firmware types that are commonly found on the primary architectures. For the x86_64 architecture, UEFI with Secure Boot configured in accordance with Microsoft's Windows certification requirements is considered a 'commonly found' firmware type.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported ARM platforms|content=Supported ARM platforms are those listed by the ARM team at [[Architectures/ARM/Supported_Platforms]].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported IoT devices|content=Supported IoT platforms are those listed by the IoT team [https://docs.fedoraproject.org/en-US/iot/reference-platforms/ here].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported IoT devices|content=Supported IoT platforms are those listed by the IoT team [https://docs.fedoraproject.org/en-US/iot/reference-platforms/ here].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported cloud environments|content=Release-blocking cloud images must boot in the [[Infrastructure/FedoraCloud|Fedora OpenStack Cloud]] and in [https://aws.amazon.com/ec2/ Amazon EC2].|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=Supported media types|content=Release-blocking live and dedicated installer images must boot when written to a USB stick with '''at least one''' of the [[How_to_create_and_use_Live_USB|officially supported methods]]. Release-blocking ARM disk images must boot when written to a medium bootable by the platform under test, according to the instructions for the platform under test.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=System-specific bugs|content=System-specific bugs don't necessarily constitute an infringement of this criterion - for instance, if the image fails to boot because of a bug in some specific system's firmware, that is unlikely to constitute a violation unless the system is an extremely popular one. See [[Blocker_Bug_FAQ]] for more discussion of this.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{hidden|header=References|content=
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KICRVUS3YHNTLHY47O5A2XL2C5YMCFIH/ demoting optical support 2016-12-06], [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/HLXHEB364LOLFHB2RDX6K4DFA4VJIWMF/ implementation 2017-01-17]
Test cases:
* [[QA:Testcase_Boot_default_install]]
* [[QA:Testcase_USB_stick_Live_luc]]
* [[QA:Testcase_USB_stick_Live_litd]]
* [[QA:Testcase_USB_stick_Live_dd]]
* [[QA:Testcase_USB_stick_DVD_litd]]
* [[QA:Testcase_USB_stick_DVD_dd]]
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}
{{anchor|expected-image-boot-behavior}}





Revision as of 18:50, 18 July 2022

Fedora CoreOS Edition requirements

These requirements apply only to the Fedora CoreOS edition.

Correct checksums

A correct checksum must be published for each official release image.

Automatic blockers

Violations of this criterion for release-blocking images are considered "automatic blockers", they do not have to go through the review process. See QA:SOP_blocker_bug_process#Automatic_blockers for more details on the automatic blocker procedure.

Initialization requirements

Release-blocking images must boot

All release-blocking images must boot in their supported configurations.

Supported FCOS devices

Supported FCOS platforms are those listed by FCOS are RPi4, Rpi3b, Allwinner, lorem ipsum.

Supported FCOS Platforms

Supported FCOS platforms are those listed by FCOShere

Expected image boot behavior

  • Release-blocking dedicated installer images must boot to the expected boot menu, and then after a reasonable timeout to the installer.
  • Release-blocking live images must boot to the expected boot menu, and then to a desktop or to a login prompt where it is clear how to log in to a desktop.
  • Release-blocking ARM disk images must boot to the initial-setup utility.
  • Release-blocking cloud images must allow login with the user authentication configuration requested during instance creation.
  • Release blocking IoT images must boot and be configurable by the Zezere utility.
  • Release blocking FCOS images must boot and install following the coreos-installer workflowNEW

Remote package sources

When using a release-blocking dedicated installer image, the installer must be able to use HTTP and HTTPS repositories as package sources. Release-blocking network install images must default to a valid publicly-accessible package source.

FCOS remote repos

In FCOS, coreos-installer should be able to fetch a remote "rootfs" if needed.




Podman container runtime

The Podman container runtime must be present on all images and installed by default when using the ISO installer. It must be possible to deploy a container image.

References