-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rhel9-ppc64le VMs offline due to NVMe failure at OSUOSL #3998
Comments
Removed rhel9-ppc64le from these jobs:
@richardlau said he'd take a look tomorrow. |
There are a couple of other jobs that use rhel9-ppc64le, but they have not runs for 5-6 days so they are more infrequent so I've not disabled them yet. I think we'll get the machine back tomorrow, if not we can exclude those as well: |
No updates on the NVMe replacement. I'm going to create new (non-NVMe) VMs. |
I've created a new test-osuosl-rhel9-ppc64_le-4 and replaced test-osuosl-rhel9-ppc64_le-3 (Ansible inventory update in #3999) with non-NVMe RHEL 9 VMs. That will give us two machines for now. My plan is to wait to see what the outlook is for getting the NVMe replaced before deciding what to do about test-osuosl-rhel9-ppc64_le-1 and test-osuosl-rhel9-ppc64_le-2. |
@richardlau thanks for the quick work. |
Got this email from OSUOSL:
This affects our rhel9-ppc64le VMs, which I had set up with NVMe storage as they had resulted in marginally faster builds:
The text was updated successfully, but these errors were encountered: