This bug was fixed in the package ubuntu-fan - 0.12.9~17.10.1
---
ubuntu-fan (0.12.9~17.10.1) artful; urgency=medium
[ Andy Whitcroft ]
* fanctl: fix config_filename when the interface does not have a width
(LP: #1737640)
-- Stefan Bader Tue, 30 Jan 2018 10:54:13
+0100
**
I think the previous test was as valid but to be completely sure I added
an additional interface to a VM, installed ifupdown and assigned the
additional interface to ifupdown control. Using 0.12.8~17.10.1 the error
was observable and the status of the interface was incorrect. Upgrading
to 0.12.9~17
I did "systemctl restart NetworkManager" and observed errors from fanctl
in my syslog. Then I upgraded ubuntu-fan to 0.12.9~17.10.1 and did
"systemctl restart NetworkManager" again, and this time there were no
such errors. However, I'm not certain that this is an adequate test, so
I'm not changing
Hello Jason, or anyone else affected,
Accepted ubuntu-fan into artful-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-
fan/0.12.9~17.10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
** Description changed:
[Impact]
* This bug effects anyone deploying LXD with juju on a machine with
interfaces configured as IP/mask. Since this is a very common use case,
SRU is needed.
[Test Case]
* Detailed process can be seen at https://paste.ubuntu.com/26169937/
[
** Changed in: opnfv
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
[SRU] /usr/sbin/fanctl: arithmetic expression: expecting p
This bug was fixed in the package ubuntu-fan - 0.12.9
---
ubuntu-fan (0.12.9) bionic; urgency=medium
[ Andy Whitcroft ]
* fanctl: fix config_filename when the interface does not have a width
(LP: #1737640)
-- Andreas Hasenack Thu, 04 Jan 2018 15:41:32
-0200
** Changed in:
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/ubuntu-fan/+git/ubuntu-fan/+merge/335745
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/ubuntu-fan/+git/ubuntu-fan/+merge/335746
--
You received this bug notification because yo
Zesty will be EOL before we can push this fix out, marking it as "won't
fix"
** Changed in: ubuntu-fan (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: ubuntu-fan (Ubuntu Bionic)
Importance: Critical => Undecided
** Changed in: ubuntu-fan (Ubuntu Artful)
Status: Inco
The bug exists in artful and bionic, it's probably just not as critical
as it was ifupdown systems like xenial and zesty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
** Changed in: ubuntu-fan (Ubuntu Artful)
Status: Confirmed => Incomplete
** Changed in: ubuntu-fan (Ubuntu Bionic)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https:
I mean, I can see the error in netplan systems like artful, but maybe
the impact there is different and local to ubuntu-fan only:
root@04-57:~# fanctl up -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting
primary: " (32-)/4 "
--
You received this bug notification becaus
I can see that ubuntu-fan in zesty, artful and bionic needs this patch,
but I can't determine if it's actually hit by this bug.
artful, for example, will use netplan in a fresh install, not e-n-i. Are
these releases really affected by this bug?
--
You received this bug notification because you a
13 matches
Mail list logo