I have a similar problem (which I describe in #36965).
With UTC=no, dhclient works during boot (therefore, I have a working connection just after boot), but fails in lease renewal. Therefore, the network connection stops working after 2 hours (the lease time).
Curiously, the problem appears since last Sunday (march, 26th), when here in Spain we changed timezone from CET (UTC+1) to CEST (UTC+2). Until now, I had UTC=no without problems. But now I need to have UTC=yes to workaround the problem.
I have a similar problem (which I describe in #36965).
With UTC=no, dhclient works during boot (therefore, I have a working connection just after boot), but fails in lease renewal. Therefore, the network connection stops working after 2 hours (the lease time).
Curiously, the problem appears since last Sunday (march, 26th), when here in Spain we changed timezone from CET (UTC+1) to CEST (UTC+2). Until now, I had UTC=no without problems. But now I need to have UTC=yes to workaround the problem.