[Bug 1311055] Re: hyper-v: DNS Server settings are not getting injected inside Ubuntu 13.10 during Failover and Test-Failover

[Martin Pitt]

I'm afraid I don't understand this bug (I don't know about HyperV).
Where do you configure point 4 and what do you expect in
/etc/resolv.conf?  Are you using static interfaces in
/etc/network/interfaces (you suggest so, but you don't show the file or
point out what's wrong in point 6) or dynamically configured ones by
NetworkManager?

Please don't keep assigning such bugs against systemd. It has nothing at
all to do with network set up.

** Package changed: systemd (Ubuntu) => ubuntu

** Changed in: ubuntu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1311055

Title:
  hyper-v: DNS Server settings are not getting injected inside Ubuntu
  13.10 during Failover and Test-Failover

Status 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]

  DNS server settigns are not getting injected inside Ubuntu 13-10 for a
  network adapter that is attached to an external network before
  Failover and is configured using static Guest IP injection during
  Failover. The settings are updated correctly inside
  /etc/network/interfaces.

  The DNS server entries updated to specified values after next reboot.

  1 Create anUbuntu-13.10 VM with external network attached to it.
  2 Check DNS entries
  cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver X.Y.Z.W
  nameserver X.Y.Z.K
  search dummy.fake.com

  3 Enable Replication.

  4 Set Failover IPv4 (static IP) settings.
  Set-VMNetworkAdapterFailoverConfiguration -ComputerName bharatl-test1 -VMName lol -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.255.0 -IPv4PreferredDNSServer 192.168.100.101 -IPv4DefaultGateway 192.168.100.1 -VMNetworkAdapterName 'Network Adapter'

  5 Do Failover.

  6 Check DNS settings.
  cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver X.Y.Z.W
  nameserver X.Y.Z.K
  search dummy.fake.com

  7 Reboot the Guest.

  8 Check DNS settings
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.100.101

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1311055/+subscriptions