Latest Gutsy Upgrade does not connect to DHCP anymore.

Same for me today.
I have success with
sudo /etc/init.d/networking restart
only if i completely power off the pc.

I try a workaround putting:
/etc/init.d/networking restart
into /etc/rc.local file.

HTH

Confirm updates 03072007 broke something on dhcp client
Same error on 3 different pc, with different nic, connected to 3 different network with different dhcpd service (Openbsd, win 2003 server ).
Yesterday these pcs was working fine.

HTH

Initially the eth0 handle was not assigned an IP address, so I added one by hand and was then able to log in from my Feisty laptop:

root@choochoo:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:EC:58:BB:AE
          inet addr:192.168.0.32 Bcast:192.168.0.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
          RX packets:124 errors:0 dropped:0 overruns:0 frame:0
          TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:17746 (17.3 KB) TX bytes:17634 (17.2 KB)
          Interrupt:18 Base address:0xd800
---snip----
I do see dhcp in memory:
root@choochoo:~# ps auxw | grep dhcp | grep -v grep
dhcp 3823 0.0 0.1 2496 636 ? S<s 11:40 0:00 dhclient3 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
--snip--
I got this in /var/log/syslog:

Jul 3 11:40:50 localhost dhcdbd: Started up.
Jul 3 11:40:51 localhost avahi-daemon[4801]: Server startup complete. Host name is choochoo.local. Local service cookie is 2306351551.
Jul 3 11:40:51 localhost kernel: [ 51.864454] cdrom: This disc doesn't have any tracks I recognize!
Jul 3 11:40:51 localhost NetworkManager: <info> eth0: Device is fully-supported using driver 'via-rhine'.
Jul 3 11:40:51 localhost NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Jul 3 11:40:51 localhost NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Jul 3 11:40:51 localhost NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
Jul 3 11:40:51 localhost NetworkManager: <info> Deactivating device eth0.
Jul 3 11:40:51 localhost avahi-daemon[4801]: Withdrawing address record for 192.168.0.3 on eth0.
Jul 3 11:40:51 localhost avahi-daemon[4801]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.3.
Jul 3 11:40:51 localhost avahi-daemon[4801]: Interface eth0.IPv4 no longer relevant for mDNS.
Jul 3 11:40:51 localhost avahi-daemon[4801]: Withdrawing address record for fe80::216:ecff:fe58:bbae on eth0.
----snip----
Please make suggestions as to other items I should display. I presume since I have my Feisty booting fine each time, and the Gutsy machine booted okay until after the last upgrade, that it really is the dhcp client, and not my dhcp server.

This is a little unorthidox, but Elart commented he confirmed but neglected to mark the status Confirmed. Perhaps a QA person can change it back if this is unacceptable.

Hey, I'm still seeing this. Isn't something like this a pretty high priority since it knocks people off the net?

me too :(

to start the network, for the time being, i just added a bash script on startup for sudo dhclient eth0 :)

I see this as fixed on my Gutsy machine with the latest partial upgrade as of I think last night. Now I'm getting all the DHCP stuff automatically again.