Bug 1764666

Summary: workaround for making Fedora installable on aarch64 and ppc64le
Product: [Fedora] Fedora Reporter: Dan Horák <dan>
Component: anacondaAssignee: Jiri Konecny <jkonecny>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: anaconda-maint-list, fweimer, hannsj_uhl, jkonecny, jonathan, kellin, kevin, mboddu, mkolman, vanmeeuwen+fedora, vponcova, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-32.13-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-07 08:59:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 245418, 1071880    
Attachments:
Description Flags
workaround none

Description Dan Horák 2019-10-23 14:46:36 UTC
Created attachment 1628504 [details]
workaround

Currently Rawhide isn't installable on aarch64 and ppc64le, because we are hitting bug #1722181 again. The reasons are increased size of TLS in current distro (resp. in the libs the python interpreter loads for anaconda to run) combined with internal limitations of TLS support on these platforms. I talked to the toolchain people and they think it can be fixed, but it will take some months before the fix is available. You can read the details in the thread starting with https://sourceware.org/ml/libc-alpha/2019-09/msg00512.html, https://sourceware.org/bugzilla/show_bug.cgi?id=25051 is the current plan for a fix.

So to unblock Rawhide on aarch64 and ppc64le, I propose we carry a patch in the Fedora anaconda rpms, that workarounds the problem. Although the change is harmless, I don't think it belongs to upstream anaconda, thus the request for a patch. I have tested the patch thru an updates image on ppc64le and it makes anaconda run again.

Comment 1 Martin Kolman 2019-10-29 18:41:56 UTC
Also the PR in question:
https://github.com/rhinstaller/anaconda/pull/2202

We ended up committing this upstream as we are not really setup for having downstream patches for Rawhide builds for an extended amount of time.

Comment 2 Kevin Fenzi 2019-10-30 22:13:09 UTC
Sadly, it doesn't seem to be working. 

It causes all the Cloud-Base images to fail. The x86_64 one I can't see any output from, but the aarch64 one I saw booting, then it says something like 'session dead' in the top left and times out. 

So, not sure what is going on here. Is the tmux env different from the one you tested with?

Comment 3 Jiri Konecny 2019-11-05 10:47:20 UTC
Hi Kevin,

Could you please provide us logs?

Comment 4 Martin Kolman 2019-11-05 10:52:12 UTC
(In reply to Kevin Fenzi from comment #2)
> Sadly, it doesn't seem to be working. 
> 
> It causes all the Cloud-Base images to fail. The x86_64 one I can't see any
> output from, but the aarch64 one I saw booting, then it says something like
> 'session dead' in the top left and times out. 
> 
> So, not sure what is going on here. Is the tmux env different from the one
> you tested with?

So what's the next step ?

1) Do we remove the hack & fixing the current issue but still breaking some aarch64 & ppc64le images ?
2) Do we remove the hack and replace it with another hack that hopefully fixes aarch64 & ppc64le while not breaking anything else ?

Comment 5 Dan Horák 2019-11-05 11:23:22 UTC
There is a typo in the workaround applied in anaconda tree, a closing quote is missing at the line end - https://github.com/rhinstaller/anaconda/blob/master/data/tmux.conf#L26

Comment 6 Jiri Konecny 2019-11-05 13:08:46 UTC
Sorry that was our fault, this is a fix:

https://github.com/rhinstaller/anaconda/pull/2206

Comment 7 Jiri Konecny 2019-11-05 13:41:25 UTC
Merged

Comment 8 Ben Cotton 2020-02-11 17:49:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 9 Dan Horák 2020-10-06 14:08:10 UTC
This can be closed, the workaround was implemented in the past release(s) and has been removed for F-33, because we have the proper fix in glibc.