The buildvm-ppc64le-20.iad2.fedoraproject.org builder seems to have issues. e.g.
https://koji.fedoraproject.org/koji/taskinfo?taskID=123690388 https://koji.fedoraproject.org/koji/taskinfo?taskID=123690570
Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/koji/daemon.py", line 1505, in runTask File "/usr/lib/python3.12/site-packages/koji/tasks.py", line 338, in run File "/usr/lib/python3.12/site-packages/koji/tasks.py", line 364, in createWorkdir File "<frozen os>", line 225, in makedirs OSError: [Errno 30] Read-only file system: '/var/tmp/koji/tasks/388/123690388'
Please fix or at least disable the builder. Thanks
Any time is good.
Hmm, that machine is in trouble – I can’t log into it from my laptop, nor directly from batcave:
nils@gibbon:~> ssh buildvm-ppc64le-20.iad2.fedoraproject.org nphilipp@buildvm-ppc64le-20.iad2.fedoraproject.org: Permission denied (publickey,gssapi-keyex,gssapi-with-mic). nils@gibbon:~>
[root@batcave01 ~][PROD-IAD2]# ssh buildvm-ppc64le-20.iad2.fedoraproject.org root@buildvm-ppc64le-20.iad2.fedoraproject.org: Permission denied (publickey,gssapi-keyex,gssapi-with-mic). [root@batcave01 ~][PROD-IAD2]#
I did a reboot of the vm from VM host, but I'm not able to login through virsh console. It asks for username over and over and never asking for password.
virsh console
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation
It seems that the reboot didn't fixed that https://koji.fedoraproject.org/koji/taskinfo?taskID=123699221
I have disabled the builder so it won't take anymore jobs.
@kevin We noticed the same on a64-20. See https://koji.fedoraproject.org/koji/taskinfo?taskID=123693229
Nevermind, I forgot to check the failed task. It's still the same machine.
I reinstalled this vm on friday. We are still trying to track down cause of this.
See https://bugzilla.redhat.com/show_bug.cgi?id=2312886 for that.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.