Bug 1474931 - Modular Server
Modular Server
Product: Fedora
Classification: Fedora
Component: Changes Tracking (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Langdon White
ChangeAcceptedF27, SystemWideChange
Depends On: 1492240 ModularServer27GA 1504212 1352587 1474910 1474935 1506851
  Show dependency treegraph
Reported: 2017-07-25 12:07 EDT by Jan Kurik
Modified: 2017-10-26 21:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Kurik 2017-07-25 12:07:28 EDT
This is a tracking bug for Change: Modular Server
For more details, see: https://fedoraproject.org//wiki/Changes/Modular_Server

The Modularity Working Group, Factory 2.0, Base Runtime, and Server Working Group would like to propose using the modular infrastructure for creating and delivering the Fedora Server Edition for Fedora 27. While we are still working through some of the kinks leading up to the release of Fedora 26, we believe that the changes to the infrastructure and technology implementations will be available with sufficient time to harden the components in time for the 27 release.
Comment 1 Jan Kurik 2017-08-10 02:18:04 EDT
On 2017-Aug-01, we have reached the Fedora 27 Change Checkpoint: Completion deadline (testable).

At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.

Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.

Incomplete and non testable Changes will be reported to FESCo for 2017-Aug-11 meeting.

Please set this bug to the MODIFIED state to indicate it is already in the testable state, or provide an update describing the current state of implementation for this Change.

Thank you,
Comment 2 Jan Kurik 2017-08-15 03:57:37 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.
Comment 3 Jan Kurik 2017-09-06 09:38:21 EDT
On 2017-Sep-05 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 27 release. At this point all the Changes not at least in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.

Thanks, Jan
Comment 4 Adam Williamson 2017-09-06 15:07:09 EDT
FWIW, AFAICT the current state of this is that we had some F27 modular composes that 'succeeded' (the last being 20170831.n.0), but none of them contained any images at all. Since 20170831.n.0, the compose has failed each day, apparently due to https://pagure.io/releng/issue/7011 . So, it has not yet been really possible to test a Fedora 27 modular Server install.
Comment 5 Adam Williamson 2017-09-06 16:14:50 EDT
Also note that the release blocking images list for F27 does not yet even exist, let alone has it been updated for this Change:

https://fedoraproject.org/wiki/Releases/26/ReleaseBlocking (F26 page)
https://fedoraproject.org/wiki/Releases/27/ReleaseBlocking (Doesn't exist)
Comment 6 Adam Williamson 2017-09-08 11:57:59 EDT
Minor update, nightly modular composes are working again, but still contain no images at all:

Comment 7 Langdon White 2017-09-11 11:04:07 EDT
Discussed in the FESCo meeting on Sept 8[1]. Revisiting at beta go/no-go (sept 14) and next FESCo (sept 15).

[1]: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/USXV5AAJJTBW673GMJNLVMVBXJA5FRV6/

Note You need to log in before you can comment on or make changes to this bug.