Bug 205117
Summary: | Installation fails on s390 when trying to log in through telnet | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthias Saou <matthias> |
Component: | anaconda | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | borgan, dcantrell, karsten, katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | s390 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-24 18:02:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matthias Saou
2006-09-04 11:15:47 UTC
It's something bizarre with telnet... I think it might be worth nuking telnet given how common ssh is at this point Any disagreement? It used to still work a couple of months ago at most... And didn't someone (yourself?) mention on a fedora list in the past few days that the reason why openssh-server generated its keys upon first startup instead of when the package gets installed was because it made a huge difference for the install time on some s390 machines? I'm just asking because I'm not sure I see the real advantage of ssh over telnet in this case... unless the keys at that point are going to be kept for the installed system? That would be a nice feature. re comment #2: it made a huge difference on our 31bit MP3000, but key generation is almost instantaneous on our zSeries machine. It's been a while since my last Hercules installation, how long does key generation take at the first boot after the installation ? btw: was this really an s390 installation or s390x ? re comment #1: telnetd aborts with a segfault (on s390x): [pid 495] mprotect(0x20000214000, 4096, PROT_READ) = 0 [pid 495] open("/etc/passwd", O_RDONLY) = 4 [pid 495] fcntl(4, F_GETFD) = 0 [pid 495] fcntl(4, F_SETFD, FD_CLOEXEC) = 0 [pid 495] fstat(4, {st_mode=S_IFREG|0644, st_size=128, ...}) = 0 [pid 495] mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x200001fd000 [pid 495] read(4, "root::0:0::/:/sbin/loader\ndebug::0:0:debug shell:/:/bin/bash\nsshd:x:74:74:Privilege-separated SSH:/var/empty/sshd:/sbin/nologin\n", 4096) = 128 [pid 495] --- SIGSEGV (Segmentation fault) @ 0 (0) --- Process 495 detached <... select resumed> ) = 1 (in [3]) --- SIGCHLD (Child exited) @ 0 (0) --- read(3, 0x80200fe8, 4000) = -1 EIO (Input/output error) I'm not sure if we should kick telnet, but have no strong objections either. I'm not against nuking telnet... just trying to make sure it won't become an issue for RHEL5 users. I used hercules with the default configuration I've included in the Fedora Extras package : CPUMODEL 3090 and ARCHMODE ESA/390 then used the files from s390/os/images/ (and not s390x of that was the question). For anyone wanting to reproduce this without any actual s390 hardware, I've made sure that the hercules package comes in a "ready to run" shape. Simply install it and follow the instructions from /usr/share/doc/hercules-*/README.fedora (for FC devel, RHEL4 and RHL 7.2). You get your own mainframe in no time! I'm running it on a 64bit Xeon 3GHz and it's not fast, but not too slow either. Thanks for the hercules info, Matthias. I'm still waiting on the zSeries Luggable from IBM. :) On nuking telnet... I'm all in favor of it. With the addition of IPv6 in to anaconda, binding telnet and/or expanding it to make it work with IPv6 is just unnecessarily annoying. I don't think the key generation time required by sshd will be that bad and users can deal with it. My two cents. I've removed telnet login support for s390 installation from rawhide. Going forward, ssh will be the only supported method for connecting to the s390 installer instance. For the RHEL-5 bug, we fixed the telnet connection problem in 5.1. I am closing this as WONTFIX since I'm not doing any more telnet support for s390 installs in Fedora. |