https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
a
I've just checked the logs on a 1.3 system I have here, and I see 
migration.sh[1189]: grep: /oem/99_custom.yaml: No such file or directory
- I assume this is the same message you get. I suspect that can be ignored and is a holdover from a previous version that did some config migration, but I'll try to verify that later.
You should see a bunch of occurrences of 
elemental... INFO ... Starting elemental version 1.1.2
... 
Running stage: rootfs[...]
... 
Running stage: initramfs
and so on as it processes the stages listed in all the files in /oem
(wild guess) It is possible the 90_custom.yaml file is misformatted somehow and it's just failing silently?
b
It's possible
I was trying to re-install and now I can't get it to connect over the previous vlan.
a
ugh ... sorry, i'm not sure what to advise on that front
b
Yeah, it could be lots of things. I still appreciate you weighing in. I had the same thoughts and so there was some validation there. 🙂
👍 1
I never figured it out, but did find out that setting the optional VLAN id in the installer caused the route to be set incorrectly. I've done that without this issue before so I have no idea why this host is so special.
😕 1
3 Views
Open in Slack
PreviousNext
Powered by