https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
a
do you have any idea ?
r
Do you have a DHCP server set up in the network? BTW, the network interface of the VM seems to be down. Maybe try 
ip link set up eth1
first?
Let’s make sure the network connectivity is good first, then we can figure out how to automate the process.
a
just had to do a dhclient on ubuntu vm, but that's not the ebest
/etc/netplans/50[...].yaml was badly generated (wrong mac addr)
maybe an issue with cloud init directly or with how harvester handle user-data cloudinit ?
r
Do you need the 
management Network
? If that’s not needed, we can get rid of 
eth0
, then 
eth1
will be 
eth0
.
cloud-init will do the trick, too, if you need 2 network interfaces
a
yes but I had to edit myself the cloudinit file, even if it's said it should be regenereted at each reboot it does not
r
do you have the original cloud-init file? the 
50[…].yaml
you mentioned.
a
no, but I will comment what I changed
Copy code
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        enp1s0:
            dhcp4: true
            match:
                macaddress: be:a4:50:c8:a6:21 // had to edit that to match the macaddr
            set-name: enp1s0
    version: 2
/etc/netplan/50-cloud-init.yaml
r
That seems not to apply to your VM. Your nic names are still 
eth0
but not 
enp1s0
. Is it a Ubuntu VM or Alpine?
Ah, I get it. The MAC address is wrong
a
I got it to work but I think there is a issue with cloud init, not sure if it's "harvester data passing" side or cloudinit script side
r
Is it reproducible?
a
I also added few command in runcmd but never worked
I'll try in few hours after the work
👍 1
r
What image are you using? I can give it a try.
a
r
Thanks
One thing to confirm: Is your first screenshot (showing the result of 
ip a
) provisioned using 
jammy-server-cloudimg-amd64.img
?
a
it was alpine
r
Okay, so the issue happened on the Alpine one? I provisioned one jammy server and did not see the issue.
Also, from the first screenshot, the instance bootstrap system seems to be Tiny Cloud, not cloud-init. Does that share the same configuration as cloud-init?
a
sorry, had some things to do IRL 😅
got resolved without any intervention so IDK
👍 1
Open in Slack
PreviousNext
Powered by