← Back to team overview

kernel-packages team mailing list archive

[Bug 1506521] Re: [Hyper-V] hv_set_ifconfig issues on Wily 15.10


This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-trusty

** Tags added: verification-needed-wily

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [Hyper-V] hv_set_ifconfig issues on Wily 15.10

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  It seems that during the Wily development, some changes have occurred that broke the hv_set_ifconfig  script.

  Please see the below details and update the script accordingly.
  From my understanding the changes in python versioning on 15.10 are causing this, and when running hv_set_ifconfig  with Python v3, it will give some code errors.

  This has been verified with the daily build from Oct 12, kernel
  4.2.0-16-generic and the matching linux-cloud-tools/common are

  # whereis hv_set_ifconfig
  hv_set_ifconfig: /usr/sbin/hv_set_ifconfig

  # /usr/sbin/hv_set_ifconfig
  /usr/bin/env: python: No such file or directory

  Indeed there is no python executable by default, only python3.

  Modifying the header for hv_set_ifconfig to use python3, returns the

  ~# /usr/sbin/hv_set_ifconfig
    File "/usr/sbin/hv_set_ifconfig", line 130
      print "==================================="
  SyntaxError: Missing parentheses in call to 'print'

To manage notifications about this bug go to: