Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

output tells me to check ara for logs, when neither ara nor wireguard are deployed yet #1837

Closed
artificial-intelligence opened this issue Nov 14, 2023 · 1 comment

Comments

@artificial-intelligence
Copy link
Contributor

example:

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?

@berendt
Copy link
Member

berendt commented Nov 22, 2023

That's related to #1849. The ARA service is part of the manager service.

@berendt berendt closed this as completed Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants