This message was deleted.
# harvester
a
This message was deleted.
w
I've seen this before, pretty sure its a false positive, you may find that once its up and running it works - reckon that while its setting up sometimes this is reported incorrectly, did it with ours, were also on AMD. Does it show with a warning in the list of nodes? As a last resort you could try rebooting the node in question.
b
it is shown as Cordoned
w
How long has it been up?
b
1.3 hours
w
Reboot it - see if it comes up - I'd say 30 mins max for a node to finish setup - usually quicker! Also gives you a chance to check bios for a sanity check.
b
okay thanks
w
(assuming you haven't already) were on 1.6.1 currently too - we'll be upgrading to 1.7.1 soon if its out now
b
I've already rebooted it to check if virtualization is okay
w
Ok - that sounds a little more worrying then. Have you raised an issue on Github? I'd raise it there with the specifics, then post a link to a thread in the chat here with a support bundle and see what they say - as this is the latest release there maybe something else happening. Have you checked longhorn is happy - nothing wacky going on with disks etc?
Is 1.7.1 actually stable yet?
I'm on 1.6.1 and its not offering the upgrade yet
b
I've just set up the node, without a, configuration for now, we will test it next week 😉
w
I see its been out 3 days... I'd raise an issue and get some specifics on there if you have this otherwise working on other identical nodes...
👍 1