Open jtagcat opened 3 years ago
thanks for letting me know
On Sun, 3 Jan 2021, 04:59 jtagcat, notifications@github.com wrote:
weaveworks/weave#3868 https://github.com/weaveworks/weave/issues/3868
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/overnode-org/overnode/issues/56#issuecomment-753490285, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6JSVIERMP5ZISGT2LH3SDSX47GVANCNFSM4VRELQIA .
I'm surprised this is still a thing with an LTS release that is over a year old. I guess the answer here is to pull down overnode.sh and change the version string for weave_version and run it locally on all my nodes? To work around you have to download the overnode.sh file and DO NOT DO an upgrade.
you have to chnag ehte weave version in the file and then do an ./overnode.sh --debug install --force
but the old version of weave is still running at this point. I'm sure there is a better way, but I just rebooted the node at this point. And the old version was still running, there is no "uninstall command"
As a side note, this bash script to do the install has reached a level of complexity that brings into question perhaps some other orchestration tool should be used such as ansible.
Did you get it working with 20.04 or not?
I'm surprised this is still a thing with an LTS release that is over a year old.
LTS stands for Long Time Support — your 18.04 installations continue working (during support time) without needing changes. 18.04 is fine till 2023 or 2028, depending on how you read it.
Of course, software development responds to current and upcoming demand. The demand here is in single digits, if even that.
For installations of overnode I support, jumping from 18.04 to 22.04 is fine.
I guess the answer here is to pull down overnode.sh and change the version string for weave_version and run it locally on all my nodes?
You could edit it once, and point it to yourself for the curl-bash.
but the old version of weave is still running at this point. I'm sure there is a better way, but I just rebooted the node at this point. And the old version was still running, there is no "uninstall command"
overnode reset
As a side note, this bash script to do the install has reached a level of complexity that brings into question perhaps some other orchestration tool should be used such as ansible.
The note expresses the superiority of bash to other orchestration tools, but I think you meant the other way around.
I agree, migrating from bash wouldn't be bad. Make a PR.
Bash was an intentional choice to keep it simple. 2/3 of the script is verification of the command line arguments. If we need orchestration spanning further of docker-compose, then Kubernetes, Docker-Swarm, etc... If I had a lot of time and this tool had wide adoption and faced a new feature request which would be impossible in Bash, then I would rewrite it in Rust.
I hacked the install script to not download and run against itself and I changed versions of weave to 2.8.1 and it still crashes with the same result. I like the idea of overnode. It makes a lot of sense for small deployments that don't need all that kubernete offers. In your defense I was stating it's crazy that WEAVE doesn't support 21.04 after it being out for almost a year. The linked issue has a patch that has been available since November 2020, so 5 months later it still hasn't been merged in and a release made? Crazy man, crazy.
Yes, weavenet issue is very disappointing. It makes me thinking if it is reliable enough to build on top of it? My current plan is to keep 18.04 and comeback to this later. Maybe I will need to switch to a different Linux flavour, which is actually used by weavenet itself, but what is it? Alpine? Core OS? If it is not reliable and should be abandoned, then, I am afraid, overnode is doomed.
To be honest, k8s is the same way — PRs are ready to merge, but there's not enough authority to do a final review and merge. :ˇ)
Is this still the case? It is broken for 20.04?
Yes.
Encountered this issue on ubuntu 22.04 because of options edns0 trust-ad
in my /etc/resolv.conf
.
What's weird is that on ubuntu 20.04 it was options edns0
and weave was working well.
I've moved on to k8s. I've abandoned my involvement in the project.
Latest Ubuntu 20.04 does not work. Breakage caused by
systemd
245.4-4ubuntu3.3
.Errors seen using overnode:
weave status
and other commands often returncurl: (52) Empty reply from server
Errors after launching:
[overnode] Error: weave is not running