user-v2 regression in master: DNS wouldn't work with existing VMs

[AkihiroSuda]

@balajiv113: I found that after upgrading from lima to 0.17.2 to HEAD-de1b3ee, DNS wouldn't work with existing VMs. I had to delete and recreate the VM for DNS to work at all. Is that expected?

Originally posted by @aaronlehmann in #1333 (comment)

[balajiv113]

I checked this. Iptables looks fine.

But the nameservers in user-data is not updated to new record after new version update

[balajiv113]

I couldn't find a way to fix this yet. One thing i noticed is the dns nameserver not updated correctly. Apart from that all were looking fine only.

Let me know if we have some ways to enforce cloud-init to update nameservers on every boot

[AkihiroSuda]

If the issue happens only on upgrade we can just let hostagent fix up DNS?

[balajiv113]

@AkihiroSuda
This is actually not happening.

Started net-user-v2 in old version. Did stop on old version. Started the same in current master DNS is working fine.

There are few other issue but unrelated to regression

[AkihiroSuda]

Thank you, seems we can close this

[aaronlehmann]

I could definitely reproduce this reliably when I reported the issue. I would create a VM with colima, upgrade lima to HEAD, and always get broken DNS. I didn't have this problem when I started with lima HEAD. I'm traveling right now but would be happy to provide more details when I get back.