| 29 Aug 2021 |
 cure | (I managed to do it without having to go there, whee) | 19:31:25 |
 Stephen304 | Nice! | 19:45:47 |
| Stephen304 | I updated my nodes in prometheus so the dashboard is looking lively again | 19:46:41 |
| cure | yeah | 19:46:45 |
| cure | my node is still down because I can't find the matching gre packages for it anymore | 19:47:01 |
| cure | sigh | 19:47:02 |
| cure | too old | 19:47:06 |
| cure | I wonder what the most efficient way is to upgrade the node | 19:47:17 |
| cure | hmm, we don't publish sysupgrade images for x86 | 19:47:37 |
| Stephen304 | What's that for? For my apu I used the ext4-combined | 19:49:39 |
| cure | yeah me too, I just wonder if I'm going to lose all config if I upgrade that way | 19:50:36 |
| cure | I suppose I can export/import | 19:50:42 |
| Stephen304 | Does sysupgrade reject it? | 19:50:59 |
| Stephen304 | I haven't tried I just wiped mine | 19:51:24 |
| cure | yeah, I run it in kvm | 19:52:22 |
| cure | and virsh is a bloody pain to deal with | 19:52:30 |
| cure | I guess I'll find out :) | 19:52:43 |
| cure | impressive, that just worked, and very quickly too | 19:59:08 |
| cure | but it did clobber the yggdrasil secrets apparently, so my ip changed, bleh | 20:07:02 |
| cure | I wonder where that is stored | 20:07:09 |
| Stephen304 | I thought the ip had to change because of ygg 4.0 changes? | 20:10:05 |
| cure | yeah, but I already had ygg 0.4.0 running | 20:10:21 |
| cure | my issue was just with the gre kernel module | 20:10:28 |
| Stephen304 | Ohh hmm | 20:10:33 |
| cure | oh, interesting, I think this is an upgrade bug in the yggdrasil 0.4.0 openwrt package | 20:28:39 |
| cure | it generates a new keypair (which you can see in /tmp/yggdrasil.conf) | 20:28:53 |
| cure | but it does not update /etc/config/yggdrasil accordingly | 20:29:09 |
| cure | so, on the next reboot, you're toast | 20:29:16 |
| cure | eek | 20:29:17 |
| cure | (I've updated the /etc/config/yggdrasil file manually on the librarynode to avoid this) | 20:37:51 |
