Forum Replies Created
-
Posts
-
Tried the same thing but on PSC and just Ubuntu. Error code:
L2B
failed lease update- all units failed priming: Exception during create for unit: b08aa09c-1f23-4b98-8fa5-ee4542ed493d Playbook has failed tasks: NSO commit returned JSON-RPC error: type: rpc.method.failed, code: -32000, message: Method failed, data: message: Network Element Driver: device psc-data-sw: out of sync, internal: jsonrpc_tx_commit357#all units failed priming: Exception during create for unit: b08aa09c-1f23-4b98-8fa5-ee4542ed493d Playbook has failed tasks: NSO commit returned JSON-RPC error: type: rpc.method.failed, code: -32000, message: Method failed, data: message: Network Element Driver: device psc-data-sw: out of sync, internal: jsonrpc_tx_commit357#Follow up – trying to set up a three node topology using the most recent versions of the VM OS (Fedora 37, Ubuntu 22, CentOS Stream 9) on the WASH site. Received the following error:
N2-F37
failed lease update- all units failed priming: Exception during create for unit: 5ea92378-e95f-4455-a54c-4bf684586fbf NoneType object has no attribute get#all units failed priming: Exception during create for unit: 5ea92378-e95f-4455-a54c-4bf684586fbf NoneType object has no attribute get#L2B
TicketReviewPolicy: Closing reservation due to failure in slice#OK, we have gotten to the point where we are adding group members. To start we have three professors (me and two others) that should be able to create/delete/etc. Should they be set as project leads and should we all be using the same slice keys?
Thanks for checking – I was able to get a manually created slice up and ssh into the VMs. Just getting used to the tools and ideas – a bit different than GENI but looks nice so far. Also trying to figure out the best strategy for keys, work storage, etc. so I am going through the posts and guides still. The goal is to get a couple of our team members into the project and able to work with the slice. Slow but sure on my end 🙂
