Build VM's becoming Read-only during build?
Hello, We are getting this issue on our builds in https://build.opensuse.org/project/show/isv:cpanel:EA4 [ 718s] /usr/src/debug/php-7.4.30/sapi/phpdbg/phpdbg_watch.c [ 718s] /usr/src/debug/php-7.4.30/sapi/phpdbg/phpdbg_watch.h [ 719s] ### VM INTERACTION START ### [ 719s] Failed to write utmp record: Read-only file system [ 719s] Powering off. [ 719s] [ 707.627964][T18932] reboot: Power down [ 719s] ### VM INTERACTION END ### [ 719s] [ 719s] lamb17 failed "build ea-php74.spec" at Tue Jun 21 15:47:31 UTC 2022. Almost all failed packages there are due to the VMs becoming read-only.. is there something we should be doing differently on our end? Regards, Cory McIntire | Lead – cPanel Application Security Team | Release Manager – EasyApache M +1 281.777.2705 | cory.mcintire@webpros.commailto:cory.mcintire@webpros.com | cPanel – a webpros company
On Jun 21 2022, Cory McIntire wrote:
Almost all failed packages there are due to the VMs becoming read-only.. is there something we should be doing differently on our end?
No, it is unrelated and does not cause any failures. You will see it on all successful builds as well. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
You’re right, my apologies, I wasn’t looking up far enough in the logfile!
Thanks for the quick response!
From: Andreas Schwab
Almost all failed packages there are due to the VMs becoming read-only.. is there something we should be doing differently on our end?
No, it is unrelated and does not cause any failures. You will see it on all successful builds as well. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
participants (2)
-
Andreas Schwab
-
Cory McIntire