fedora-infrastructure

#10625 z/vm s390x builders down
Closed: Fixed by kevin. Opened by kevin.

Closed: Fixed
Reopen Issue

After mass update/reboots yesterday none of the z/vm s390x builders came back up. ;(

Logging into one on the console shows that it can't see any network devices. ;(

I tried various things with cio_ignore and znetconf without much luck. I tried pinging my main mainframe contact on chat, but he's apparently out...

CC: @sharkcz in case you have any ideas.

@kevin : is that using a bridge interface ?
Is it configured to be a bridge with the chzdev command ?
https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lkdd/lkdd_t_qeth_wrk_hsbrdg.html

for example, on the CentOS Stream s390x main LPAR (used as a kvm hosts for the builders) the following command has to be issued (I have a init script taking care of that) : /usr/sbin/chzdev -a 0.0.1800 bridge_role=primary

update: realized you said you don't even see any network device so can't be that .. worth verifying in the LPAR profile that active profile still references the nic assignement I guess
Edited by arrfab

Nope, thats the kvm version... these are each their own z/vm instances... so they should have their own network adapters. ;(

for the record, /etc/sysconfig/network-scripts/ifcfg-enc900 is missing the s390 specific configs

LAYER2=1
SUBCHANNELS=0.0.0900,0.0.0901,0.0.0902
NETTYPE=qeth

Thanks for fixing all these @sharkcz!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.