You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been slowly expanding my room-assistant cluster (up to 6 nodes now, with a 7th on the way to complete it) and after 4 nodes and a botched upgrade to 2.13 I switched to using Ansible, which has been amazing.
I have noticed one thing, which is that the first time a new Pi Zero W is provisioned by Ansible, the whole thing hangs after the room-assistant installation step. SSHing to the node in question reveals that room-assistant is installed (the launcher is available at /opt/nodejs/bin/room-assistant), there are no other SSH sessions in progress on the new Pi, and yet Ansible has failed to continue to the next step. Killing and re-running Ansible allows it to complete and bring the cluster back up.
I'm not sure exactly how to go about debugging this, and it's at most a minor inconvenience, but I thought I would document it here in case others have the same issue.
The text was updated successfully, but these errors were encountered:
I've been slowly expanding my room-assistant cluster (up to 6 nodes now, with a 7th on the way to complete it) and after 4 nodes and a botched upgrade to 2.13 I switched to using Ansible, which has been amazing.
I have noticed one thing, which is that the first time a new Pi Zero W is provisioned by Ansible, the whole thing hangs after the room-assistant installation step. SSHing to the node in question reveals that room-assistant is installed (the launcher is available at
/opt/nodejs/bin/room-assistant
), there are no other SSH sessions in progress on the new Pi, and yet Ansible has failed to continue to the next step. Killing and re-running Ansible allows it to complete and bring the cluster back up.I'm not sure exactly how to go about debugging this, and it's at most a minor inconvenience, but I thought I would document it here in case others have the same issue.
The text was updated successfully, but these errors were encountered: