This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1311071
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1311071
Title:
hyper-v: IP Injection setting are not correctly populated inside
Ubuntu 13.10 guest during Failover and Test Failover when using more
than one interfaces for IP Injection
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
[HyperV Replica :: http://technet.microsoft.com/en-us/library/jj134172.aspx]
[Guest IP Injection ::
http://blogs.technet.com/b/virtualization/archive/2012/05/29/inject-ip-address-into-the-vm-during-failover.aspx]
After failover only the Injected IP settings of the last interface is
retained inside /etc/network/interfaces
Repro Steps:
1) Create Ubuntu 13.10 virtual machine.
2) Enable Replication.
3) Attach two network adapters on recovery.
'Network Adapter' and 'Adapter2'
4) Assign Failover IP settings to both these adapters.
Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName
$vmname -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.0.0
-IPv4PreferredDNSServer 192.168.100.101 -IPv4AlternateDNSServer 192.168.100.102
-IPv4DefaultGateway 192.168.100.1 -VMNetworkAdapterName 'Network Adapter'
Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName
$vmname -IPv4Address 192.168.100.20 -IPv4SubnetMask 255.255.255.0
-IPv4PreferredDNSServer 192.168.100.201 -IPv4AlternateDNSServer 192.168.100.202
-IPv4DefaultGateway 192.168.100.2 -VMNetworkAdapterName 'Adapter2'
5) Do Failover.
Check contents of eth0
cat /var/lib/hyperv/ifcfg-eth0
HWADDR=00:15:5D:38:4E:30
DEVICE=eth0
BOOTPROTO=none
IPADDR0=192.168.100.10
NETMASK0=255.255.0.0
GATEWAY=192.168.100.1
DNS1=192.168.100.101
DNS2=192.168.100.102
Check contents of eth1
# cat /var/lib/hyperv/ifcfg-eth1
HWADDR=00:15:5D:38:4E:31
DEVICE=eth1
BOOTPROTO=none
IPADDR0=192.168.100.20
NETMASK0=255.255.255.0
GATEWAY=192.168.100.2
DNS1=192.168.100.201
DNS2=192.168.100.202
6) Look into contents of /etc/network/interfaces
# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
# The following stanza(s) added by hv_set_ifconfig
auto eth1
iface eth1 inet static
address 192.168.100.20
netmask 255.255.255.0
gateway 192.168.100.2
dns-nameservers 192.168.100.201 192.168.100.202
#End of hv_set_ifconfig stanzas
7) Only IP settings for the last interface i.e., eth1 in our case are intact.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311071/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
