Failed Deployments on NodeID_7976 #86

Open
opened 2026-03-30 07:57:13 +00:00 by Sherwint · 2 comments
Member
  • Made a few attempts to deploy on one of Robert's nodes_ ID_7976 and it ends with this error msg on all attempts - Failed to send request to twinId 15343 with command: zos.deployment.get, payload: {"contract_id":2085855} 0 deployment not found
  • The only errors I'm seeing from Grafana is about the contract failing to decomission. Post which the logs return to normal.

image

- Made a few attempts to deploy on one of Robert's nodes_ ID_7976 and it ends with this error msg on all attempts - `Failed to send request to twinId 15343 with command: zos.deployment.get, payload: {"contract_id":2085855} 0 deployment not found` - The only errors I'm seeing from Grafana is about the contract failing to decomission. Post which the logs return to normal. ![image](/attachments/f5748700-19bf-4905-a1f8-173b9ff41e5d)
671 KiB
Member

it looks the provisiond service hangs after this step provisiond: 2026-03-29T04:27:18Z info provisioning workload workload-id=3309-2086709-vmhyphq workload-type=zmachine for about 3 mins then it panics due to context timesout

this could be coming from different steps, setup mycelium tapdev, starting cloud-hypervisor service or takes time to download the flist from the hub. still investigating the root cause

also noticed this node doesn't have any live vms, so will need to check its history further as well

it looks the provisiond service hangs after this step `provisiond: 2026-03-29T04:27:18Z info provisioning workload workload-id=3309-2086709-vmhyphq workload-type=zmachine` for about 3 mins then it panics due to context timesout this could be coming from different steps, setup mycelium tapdev, starting cloud-hypervisor service or takes time to download the flist from the hub. still investigating the root cause also noticed this node doesn't have any live vms, so will need to check its history further as well
Member

noticed similar behavior on node 1610 as well, pushing a patch to mainnet with a fix mycelium/circle_ops#738

noticed similar behavior on node 1610 as well, pushing a patch to mainnet with a fix https://forge.ourworld.tf/mycelium/circle_ops/issues/738
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mycelium/circle_support#86
No description provided.