[all] too many NODE_FAILURES on periodic CI jobs
Bug #1917418 reported by
Bhagyashri Shewale
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
https:/
We are getting below issue and failed to build node:
1. Detailed node error: Build of instance <instance-id> aborted: Failed to allocate the network(s), not rescheduling / "Failed to allocate the network(s), not rescheduling"
2. nodepool.
3. No valid host found
4. Quota exceeded for ram
First one got resolve.
Changed in tripleo: | |
importance: | High → Critical |
description: | updated |
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Looking at the nodepool logs, it all points to some error in the cloud provider side. I have opened a ticket on Vexxhost to track this.