[4.19-9.6]: ostree.sync kola test fails on s390x

[marmijo]

In s390x, the ostree.sync kola test is failing in the 4.19-9.6 stream with the following output.
This test passed successfully in a recent run, but fails most of the time.

[2025-01-27T16:43:40.293Z] --- FAIL: ostree.sync (604.38s)
[2025-01-27T16:43:40.293Z]         sync.go:201: Got NFS mount.
[2025-01-27T16:43:40.293Z]         sync.go:229: Set link down and rebooting.
[2025-01-27T16:43:40.293Z]         cluster.go:151: Running as unit: run-rd0aaf58e6eb14d4fb456769f3bbb393f.service
[2025-01-27T16:43:40.293Z]         harness.go:106: TIMEOUT[10m0s]: ssh: sudo sh /usr/local/bin/nfs-random-write.sh
[2025-01-27T16:43:40.293Z]         harness.go:106: TIMEOUT[10m0s]: ssh: cat /proc/cmdline
[2025-01-27T16:43:40.293Z] FAIL, output in /home/jenkins/agent/workspace/build-arch/tmp/kola-0nsQt/kola/rerun

The journal log of one of the recent failed s90x build jobs shows:

Jan 27 16:33:36.020474 coreos-teardown-initramfs.service[1276]: info: taking down network device: enc3
Jan 27 16:33:36.021223 coreos-teardown-initramfs.service[1296]: RTNETLINK answers: Operation not supported
Jan 27 16:33:36.023099 coreos-teardown-initramfs.service[1276]: info: flushing all routing
Jan 27 16:33:36.025557 coreos-teardown-initramfs.service[1276]: info: no initramfs hostname information to propagate
Jan 27 16:33:36.027205 coreos-teardown-initramfs.service[1276]: info: no networking config is defined in the real root

journal.txt

console.txt

[marmijo]

Also, for completeness, this test was recently added to coreos-assembler in: coreos/coreos-assembler#3998

[HuijingHei]

I will take it, @marmijo can you sync this to jira and assign it to me, I have no permission to do the sync, thanks!

[marmijo]

/jira

[jlebon]

I think you're looking for:
/label jira

@HuijingHei, next time try that yourself too. If you don't have access, we should look into it.

[openshift-ci]

@jlebon: The label(s) /label jira cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

I think you're looking for:
/label jira

@HuijingHei, next time try that yourself too. If you don't have access, we should look into it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jlebon]

Hmm, I think we still have to wire it up for issues. Anyway, added it manually for now.