eth devices change numbering without notice to user

[rababb]

I setup Ubuntu 7.10 on VMWare Server. After getting some initial packages installed, I planned to use this install as a template for other Ubuntu servers with only slight modifications. After copying the VMWare files to a new folder, loading the newly copied folder into inventory, and then running the new copy the eth0 adapter no longer worked. The problem appears to be related to the assignments entered into /etc/udev/rules.d/70-persistent-net.rules.

When VMWare creates the Ethernet interface, it creates a random MAC address based upon the UUID for the instance. Whenever a VMWare is copied and run again from a new location (or new server) a new UUID can be created which then changes the MAC address. This causes the behavior identified.

Unfortunately there is no easy way to track this problem down because during Ubuntu boot up the system will find the eth device(s) as eth0...ethN, but then based upon that persistent rules file will rename the device sometime later in the boot process without notice to the user.

This seems to have been introduced between Feisty and Gutsy versions as my Feisty systems do not contain the 70-persistent-net.rules file.

[Leann Ogasawara (leannogasawara)]

Hi rababb,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Care to test the most recent Hardy Heron 8.04 release - http://www.ubuntu.com/getubuntu/download . Please let us know your results. Thanks in advance.

[rababb (rob-rbabb)]

Hi Leann,

Yes, I have migrated several systems to the newer 8.04 code and it is
still an issue.

Regards,

Rob Babb

Leann Ogasawara wrote:
> Hi rababb,
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Care to test the most recent Hardy Heron 8.04 release -
> http://www.ubuntu.com/getubuntu/download . Please let us know your
> results. Thanks in advance.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michael Nagel (nailor)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!