+++ This bug was initially created as a clone of Bug #641986 +++
Description of problem:
Installation via CTC devices is currently not possible.
First problem is that NM doesn't mark those devices as Network devices.
In src/nm-udev-manager.c:net_add the content of p.e.
/sys/devices/ctcm/0.0.0150/net/ctc0/type is read. As it is a pointopoint device it doesn't have '1' in it but '256', so the check for 'if ((etype != 1)' fails.
Second problem that I couldn't pin down yet is that nm_connection_verify in the wired_connection_from_ifcfg function fails and afterward the ctc0 network interface gets shut down.
This is currently blocking installations with the current NM on the hercules s390x emulatory, which would be very helpful for other Fedora maintainers to track down bugs in their packages as most of them don't have access to a real mainframe.
--- Additional comment from firstname.lastname@example.org on 2010-10-18 09:21:20 EDT ---
Created attachment 454105 [details]
Add support for ctc devices so that anaconda can install from those
I wasn't sure how to detect a network interface is of type CTC, so I'm currently relying on the interface name.
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
This enhancement request was evaluated by the full Red Hat Enterprise Linux
team for inclusion in a Red Hat Enterprise Linux minor release. As a result
of this evaluation, Red Hat has tentatively approved inclusion of this feature
in the next Red Hat Enterprise Linux Update minor release. While it is a goal
to include this enhancement in the next minor release of Red Hat Enterprise
Linux, the enhancement is not yet committed for inclusion in the next minor
release pending the next phase of actual code integration and successful Red
Hat and partner testing.
So the fix for 6.2 would be a squashed combination of the following two upstream commits from the NM_0_8 branch:
they should apply with minimal changes since this part of the code hasn't moved much since 0.8.1.
On the config and libnm-util side we'd want to backport:
I was able to install RHEL6.2-20110815.n.0 on s390x via a CTC device. After reboot to installed system, the CTC device was up and running:
root@rtt6 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ctc0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 32760 qdisc pfifo_fast state UNKNOWN qlen 100
inet 192.168.1.1 peer 192.168.1.2/32 brd 192.168.1.1 scope global ctc0
[root@rtt6 ~]# cat /etc/sysconfig/network-scripts/ifcfg-ctc0
[root@rtt6 ~]# rpm -q NetworkManager
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
NetworkManager did not recognize IBM CTC (Channel-to-Channel) devices, which made it impossible to install Red Hat Enterprise Linux on IBM S/390 machines which used CTC devices. NetworkManager now detects these devices properly, with the result that Red Hat Enterprise Linux can be installed on such machines.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.