Public bug reported:
I have a Ubuntu 10.04 LTS server with a NAT network adapter. It's a VM
under Oracle OneBox.
If I alter /etc/network and assign a static IP to eth1 and then do sudo
/etc/init.d/networking restart, I get this:
* Reconfiguring network interfaces...
SIOCADDRT: File exists
Failed to bring up eth1.
This SIOCADDRT is terribly misinforming the user. There is no problem
file some file that exists. The problem is that I am assigning a static
IP to an adapter that doesn't support it.
This message is worse than useless because, not only does it fail to
provide useful information, it may send admins down a irrelevant rat
hole, trying to verify the existence of some random file.
You may ask, "Why eth1 and not eth0?" I created a VM and later ran into
a possible OneBox bug where it could no longer start the VM (several
reports of it in the OneBox forums lately). I deleted the VM instance
but preserved the drive. The old VM instance had a bridged network
adapter. I made a new VM instance and accidentally left the network
adapter at NAT. I think it's eth1 because Ubuntu detected a new network
adapter.
** Affects: ubuntu
Importance: Undecided
Status: New
--
SIOCADDRT error message misinforms user
https://bugs.launchpad.net/bugs/638963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
