-
Notifications
You must be signed in to change notification settings - Fork 368
runtime error due to need for cleanup #36
Comments
Been trying to recreate this issue, but not seeing it. I ran the cleanup.sh, which deleted the nodes, then reran setup.sh successfully. |
thanks for taking a look @Mhart12! @dlespiau may know more: but somehow I got into an intermediate state when running previous |
I'm getting the same issue, my guess is the leftover Initial run:
Subsequent run:
OS: Ubuntu 20.04 LTS
Result of
If I can provide more information that can help reproduce, please let me know. EDIT: I will also mention I had to manually install
|
observe:
Which is a non obvious error message in the context of the actual situation: which was that the VMs aren't actually running (and need to therefore be cleaned up with
cleanup.sh
).The containers
firekube-node[01]
still exist, they are just not running.The text was updated successfully, but these errors were encountered: