Joseph Weigl
Joseph Weigl
@daniel-lo same for me. update is reported as successful but actually nothing is updated.
@daniel-lo i found the problem on my setup. when you go to the update page there is a update server input field on the top. there was the internal docker...
@daniel-lo i guess that not true.. if you check the logs you see that you are uploading your desired files to tasmoadmin and then let the devices fetch this file...
@daniel-lo yes ;)
@daniel-lo can you access the tasmoadmin webinterface with the entered IP and the port? i guess this should work.. maybe you need also to check the SSL option?
@daniel-lo okay.. thats odd.. sounds you have a different issue. sorry that i couldn't help
Hi, in our case it looks like this:  the status is going from `True` to `False` and `Unknown` for some kinds.. But all are recovering after a few minutes.....
@stefanprodan thanks for the explanation 👍 at least that matches the behaviour i'm seeig.. so for now i can implement a workaround for our alerting to observe a bit longer...
@stefanprodan I'm not familiar with the kubectl diff and which options to use but here is some input: kubectl diff --server-side -k . --force-conflicts=true -> i see the same deletes...
not directly. because know i'm unable to run a generic task for my current arch/os and also i can not run a task which will build all binaries for the...