Full VMs are failing to deloy - Robert #83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I go to Deploy, Virtual Mahcines and click on the create virtual machine button. I selecht node 7933 to create a VM on. Nowhere I use a domain or node 1, 13 or 50. But...while it is creating that VM on node 7933 I see on the status bar on the dashboard that it briefly touched one of those nodes in Belgium. thatis NOT me doing that, it it the Threefodl script that geneartes VM's. No domains are involved
Error Message:
Failed to deploy the deployment on node 1. Failed to send request to twinId 7 with command: zos.deployment.deploy, payload: {"version":0,"metadata":"{\"version\":3,\"type\":\"network\",\"name\":\"nwkd8ge\",\"projectName\":\"fullvm/tempmarco\"}","description":"","twin_id":6629,"expiration":0,"workloads":[{"version":0,"name":"nwkd8ge","type":"network","data":{"__type":"network","subnet":"10.20.2.0/24","ip_range":"10.20.0.0/16","wireguard_private_key":"zEc31cJdAX/mTh+6+6rA5uajjQhAr4P/XNtucIhhoOM=","wireguard_listen_port":21777,"node_id":1,"mycelium":{"hex_key":"6e16f8461098474342725e757ed431972a83b129f7d3f943a4b935cac4797432","peers":[]},"peers":[{"subnet":"10.20.3.0/24","wireguard_public_key":"Or0TgYT2HRCsmbhP38oPCJnrspUUdJhvXQiq2+UBAzg=","allowed_ips":["10.20.3.0/24","100.64.20.3/32"],"endpoint":""},{"subnet":"10.20.4.0/24","wireguard_public_key":"mu8VrSgF9RjbZybZ5QjC/HZpqtWnfNn/U2B/W5u4QnE=","allowed_ips":["10.20.4.0/24","100.64.20.4/32"],"endpoint":""}]},"metadata":"{\"version\":3,\"user_accesses\":[{\"node_id\":1,\"private_key\":\"QeghGlEy0QUyy7yzXO/Sc/8nYKo9cfkHudstaEJsGpI=\",\"subnet\":\"10.20.3.0/24\"}]}","description":""}],"signature_requirement":{"requests":[{"twin_id":6629,"weight":1,"required":false}],"signatures":[{"twin_id":6629,"signature":"ba3fdf00ea3768508cae3464f175310ce59dda26a45374e058bec81c1cacf569f3d4e53d6f31b9790294569c101071232aa592c62573341949f6025b5e6f8f86","signature_type":"sr25519"}],"weight_required":1},"contract_id":2085166} 0 failed to verify signatureThis happens after a twin transfer ?
zos create twindb with a 6-hour in-memory expiration, so once a twin is fetched from tfchain, its PublicKey (account public key) is cached and reused for the TTL duration.
the expected behavior that after a twin transfer we will have a signature verification issue up to 6-hours (can be way less, it just depend on the time the node fetched his address from tfchain)
Please try again and let me know if this is resolved now.
I'm following up to enquire with the user. Will share an update when I hear back. Thanks for looking into this.