From Fedora Project Wiki
(issues found in F-22 Beta RC1(20150419))
(Release Notes)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
<!-- = Fedora/s390x specific Release Notes = -->
 
<!-- = Fedora/s390x specific Release Notes = -->
 +
 +
= Downloads =
 +
 +
Please download from
 +
 +
* http://download.fedoraproject.org/pub/fedora-secondary/releases/22/Server/s390x/
 +
* http://download.fedoraproject.org/pub/fedora-secondary/releases/22/Everything/s390x/os/
 +
 +
or your mirror carrying Fedora secondary architectures from
 +
 +
* https://admin.fedoraproject.org/mirrormanager/mirrors/Fedora/22/s390x
 +
 
= Release Notes =
 
= Release Notes =
  
 
for older notes see [[Architectures/s390x/21]]
 
for older notes see [[Architectures/s390x/21]]
  
* ...
+
* [https://bugzilla.redhat.com/show_bug.cgi?id=1212374 1212374] - the GHC ABI hash changed during the F-22 development cycle, so there are broken dependencies between the various ghc-* packages. So please either continue using F-21 or wait for F-23 if you depend on the Haskell language stack.
 +
* [https://bugzilla.redhat.com/show_bug.cgi?id=1211638 1211638] - it can affect the ability to provide the Domain Controller Role
 +
* [https://bugzilla.redhat.com/show_bug.cgi?id=1227798 1227798] - using LDL formatted DASDs leads to a crash in the installer, please use CDL DASDs instead
  
 
= Developer information =
 
= Developer information =
Line 49: Line 63:
 
'''Boot status:''' OK
 
'''Boot status:''' OK
  
== issues found in F-22 Beta RC1(20150419) ==
+
== issues found in F-22 Beta RC1 (20150419) ==
 
using anaconda-22.20.9-1.fc22, tigervnc-1.4.3-4.fc22
 
using anaconda-22.20.9-1.fc22, tigervnc-1.4.3-4.fc22
  
Line 56: Line 70:
  
 
'''Installation status:''' OK (graphical), N/A (kickstart with VNC), N/A (kickstart with text)
 
'''Installation status:''' OK (graphical), N/A (kickstart with VNC), N/A (kickstart with text)
 +
 +
'''Boot status:''' OK
 +
 +
== issues found in F-22 Beta RC2 (20150419) ==
 +
* same as RC1, only the file names contain 22_Beta instead of 22_Beta_RC
 +
* declared as GOLD
 +
 +
== issues found in F-22 TC1 (20150512) ==
 +
using anaconda-22.20.12-1.fc22
 +
 +
'''Installation status:''' OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
 +
 +
'''Boot status:''' OK
 +
 +
== issues found in F-22 RC3 ==
 +
using anaconda-22.20.13-1.fc22
 +
 +
'''Installation status:''' OK (graphical), OK (kickstart with VNC), OK (kickstart with text)
  
 
'''Boot status:''' OK
 
'''Boot status:''' OK

Latest revision as of 17:55, 3 June 2015


Downloads

Please download from

or your mirror carrying Fedora secondary architectures from

Release Notes

for older notes see Architectures/s390x/21

  • 1212374 - the GHC ABI hash changed during the F-22 development cycle, so there are broken dependencies between the various ghc-* packages. So please either continue using F-21 or wait for F-23 if you depend on the Haskell language stack.
  • 1211638 - it can affect the ability to provide the Domain Controller Role
  • 1227798 - using LDL formatted DASDs leads to a crash in the installer, please use CDL DASDs instead

Developer information

Global info

Image composes are run on F-22 with

  • pungi-3.13-1.fc22
  • lorax-22.5-2.fc22

since 20150331 using

  • pungi-3.14-1.fc22
  • lorax-22.7-1.fc22

The test composes are available from http://s390.koji.fedoraproject.org/compose/

issues found in F-22 Test 20150312

using anaconda-22.20.1-1.fc22, python-blivet-1.0-1.fc22, pykickstart-1.99.66-1.fc22

Known issues:


Installation status: OK (graphical), N/A (kickstart with VNC), N/A (kickstart with text)

Boot status: OK

issues found in F-22 Beta TC1 (20150331)

using anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22

Known issues:

Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)

Boot status: OK

issues found in F-22 Beta TC2 (20150407)

using anaconda-22.20.8-1.fc22, libblockdev-0.8-1.fc22, tigervnc-1.4.3-2.fc22

Known issues:

Installation status: OK (graphical), N/A (kickstart with VNC), N/A (kickstart with text)

Boot status: OK

issues found in F-22 Beta RC1 (20150419)

using anaconda-22.20.9-1.fc22, tigervnc-1.4.3-4.fc22

Known issues:

  • CTC networking requires manual actions to workaround bugs 1212061 and 1212118

Installation status: OK (graphical), N/A (kickstart with VNC), N/A (kickstart with text)

Boot status: OK

issues found in F-22 Beta RC2 (20150419)

  • same as RC1, only the file names contain 22_Beta instead of 22_Beta_RC
  • declared as GOLD

issues found in F-22 TC1 (20150512)

using anaconda-22.20.12-1.fc22

Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)

Boot status: OK

issues found in F-22 RC3

using anaconda-22.20.13-1.fc22

Installation status: OK (graphical), OK (kickstart with VNC), OK (kickstart with text)

Boot status: OK