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
make manager
[...]
+ osism netbox import
2023-11-14 10:26:45 | INFO | Task 31df09f5-0c22-44e7-a9bf-c3a3672ec329 is running. Wait. No more output.
+ osism netbox init
2023-11-14 10:26:51 | INFO | Task a99be77f-0500-4a66-a37a-4349a974589c is running. Wait. No more output. Check ARA for logs.
at this point ara does not even run just yet, as can be seen in a separate console:
make console
dragon@testbed-manager:~$ docker ps | grep ara
dragon@testbed-manager:~$
it's also not possible at this step to check ara - if it would have been deployed yet - because there is no wireguard config there either:
dragon@testbed-manager:~$ l /home/dragon/wireguard-client.conf
ls: cannot access '/home/dragon/wireguard-client.conf': No such file or directory
should we deploy ara and wireguard earlier in the deployment process or is this a (documentation) bug?
The text was updated successfully, but these errors were encountered:
example:
at this point ara does not even run just yet, as can be seen in a separate console:
it's also not possible at this step to check ara - if it would have been deployed yet - because there is no wireguard config there either:
should we deploy ara and wireguard earlier in the deployment process or is this a (documentation) bug?
The text was updated successfully, but these errors were encountered: