Re: Race condition/bug in cloud-init/dhcp?

A, and there is at least on case, where wrong transaction ID is normal: [I/42 dhcp]: Waiting for IP... [I/42 dhcp]: Waiting for IP... [W/245 dhcp]: Got packet with wrong transaction ID (1658613712, 83593658) OSv sends first discover. DHCP server takes some time, to check if lease is actually

Re: Race condition/bug in cloud-init/dhcp?

The idea of releasing IP during boot was really bad - any code doing TCP/IP during that time could be affected. I saw problem with nfs-mount.so, for example. Sorry for the inconvenience. Justin -- You received this message because you are subscribed to the Google Groups "OSv Development"

Re: Race condition/bug in cloud-init/dhcp?

> On 7 Jan 2017, at 08:03, Rick Payne wrote: > I wondered if it was something to do with getting the hostname via > cloud-init, and re-doing the DHCP? I can’t say I’ve tried this before that > recent change went in - if I get a chance later I will do… So looks like I

Race condition/bug in cloud-init/dhcp?

I’ve started playing with cloud-init, and I’m occasionally seeing things halt during startup. Not very frequently, but frequently enough that it looks like some race condition. The indicator is the DHCP message ‘Got packet with wrong transaction ID’. Anyone else seen this? BSD shrinker: