Quick install and upgrades to master or release_v0...
# upgrades
o
The current instructions for quick installation and upgrades don't seem to work. The nm-quick.sh script seems to require additional parameters (e.g. -b version -t master) to run. But this generates a "manifest not found" error. The nm-upgrade.sh script simply barfs and throws a 404. Could you guys kindly check these scripts?
b
there is a pr out for the isntallscript, can you post where the upgrade is failing
o
When I have some time today, I'll pull some logs together. But installation scripts should probably be better tested on an automated basis with a scripted unit test. This kind of thing is the first exposure to Netmaker to a whole bunch of people, and it doesn't give a lot of confidence when it stops customers dead in their tracks.
Tried to replicate it now with the following, directly from the online documentation at https://github.com/gravitl/netmaker#get-started-in-5-minutes: sudo wget -qO /root/nm-quick.sh https://raw.githubusercontent.com/gravitl/netmaker/master/scripts/nm-quick.sh && sudo chmod +x /root/nm-quick.sh && sudo /root/nm-quick.sh This now works without error in upgrading from release_v0.17.1 to release_v0.18.7.
My reported issue can be closed. Thank you.
The current fixes on master for nm-quick.sh have done the trick.
b
glad you got it working.
i do agree with this, my personal expierence with netmaker is when it works its great. but once you start touching it something will probably go wrong, and upgrades aren't completely seamless. these types of issues being common on an early project like this. netmaker right now is a early product in 0.x.x and seems to have the right team for it to mature into a really stable piece of kit.
o
I like it quite a lot. But as its USP is to help construct and maintain networks over WireGuard, I hope that it takes as many cues as possible from how WireGuard itself is delivered.
Looks like going from 0.17.1 to 0.18.7 destroys all of the existing node and network definitions without possibility of recovery, breaks UI on handling egress, and causes issues between external and internal nodes. I'll have to downgrade. This is not progress for my use cases.
a
how did you downgrade? i saw some backup volumes. not sure if those are from the 0.17.1.