This message was deleted.
# elemental
a
This message was deleted.
m
Okay so I think I am getting closer, I added a VM in Harvester, booted from the ISO, that made it show up in the machine inventory, which allowed me to use the create cluster section. This was all with the defaults, however it got stuck waiting for calico. Unsure if perhaps it was underpowered (after all I am just testing at this point) I tried again, this time I also updated the endpoint cloud config as I noticed that although it seemed to process the Harvester cloud config and create a user from it, it didn't grant any of the additional user options (sudo privileges) that was supposed to add. However after booting from the new ISO and creating a new cluster it just sits at "waiting for agent to check in and apply initial plan", I tried looking using the default root/root combo and the one I added, since neither worked I am guessing the altered cloud config must have errored, but can't really tell since I can't login. Looking now at the resultant endpoint config, it is mangled from what I originally typed in, I will see if uploading it as a file instead of in the editor makes any difference in how it is parsed.
w
Hi @microscopic-horse-63655! Yep, as you wrote the way to add Elemental nodes in Harvester is to boot them using the ISO which registers the nodes in Rancher and from there the nodes can be added to clusters.
As for the "Waiting for agent".. this usually happens when the elemental node cannot register to the rancher cluster for some reason. I'm assuming you followed the quickstart guide since you mention root/root.
Are you able to ping the node? If you could post the MachineRegistration used that would also be helpful in debugging this!
m
Okay, interestingly I deployed it using the latest version of Teal and it worked this time. I didn't realize the drop down for building the ISO is in reverse version order.
I guess I should say this was without modifying anything cloud config related just using the default in the editor. For whatever reason the editor resorts stuff and after saving would have items in the wrong format so I skipped trying to do that.
w
Aha, that's interesting! We've tried being backwards compatible, but we are probably not testing older ISOs with newest version of the operator, might be something that has slipped through, I will try that!
m
Oh one other thing, is 1.4.2 for the UI extension supposed to be available? It shows up under the Apps section in Rancher, but if you try updating it complains that the namespace (I think) is incorrect. You can update the other components to 1.4.2 it seems but maybe this is on purpose cause its not quite ready yet?
w
The UI extension follows it's own versioning.. I think the next to be released is 1.3.1: https://github.com/rancher/elemental-ui/releases
m
Ah I see, the nomenclature is a little confusing I guess, it shows 1.3.1+up1.4.2, which I interpreted as it was going from 1.3.1 to 1.4.2. Thanks for the help, I think I am starting to get the hang of it!
👍 1
w
Glad to hear it! 🙂