I'm marking this as invalid in snappy as it doesn't seem related to
snapd proper.
** Changed in: snappy
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network configuration
To manage notifications ab
In Snappy, as a workaround, you can add a
/etc/systemd/system/usr-sbin-fanctl.mount
with contents:
[Unit]
Description=suppress fanctl issues
Before=networking.service
After=-.mount
[Mount]
What=/bin/true
Options=bind
Where=/usr/sbin/fanctl
[Install]
RequiredBy=-.mount
--
You received this bug
This bug was fixed in the package ubuntu-fan - 0.9.1
---
ubuntu-fan (0.9.1) xenial; urgency=medium
[ Andy Whitcroft ]
* fanatic: fix legacy command line form syntax error (LP: #1584150)
* fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)
[ Jay
@Uli, these users needs to test so when they will have any trouble they would
probably bump this or another bug report.
I do not like the concept but this is what we have now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Confirmed "/usr/sbin/fanctl net start ens3" now exits 0 in the face of
an empty configuration.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Version 0.9.1 fixes this bug for armhf and aarch6. I'm using Docker on
both platforms and I'm happy to see that the network startup won't get
confused any more by ubuntu-fan (like version 0.9.0 did). This is what I
can confirm.
What I cannot conform is if 0.9.1 has any impact for people who rely o
@Mark, @Uli:
Testing the problematic state would be to install docker.io and enable it ie:
apt install docker.io
systemctl enable docker
To test:
reboot
ifdown ens3 && echo "OK"
ifup ens3 && echo "OK"
The test commands will result in two lines with OK at the end if everything is
right.
On ubuntu
On 13/07/16 04:32, Uli Middelberg wrote:
>> @Uli, It's an automated dependency.
> I know.
>
> The question is: Should I modify /etc/network/fan if I'm using private
> IP addresses outside of 10.254/16, 172.16/12, 192.168/16, e.g. 10/24 ?
The key thing with the fan is that all the machines particip
> @Uli, It's an automated dependency.
I know.
The question is: Should I modify /etc/network/fan if I'm using private
IP addresses outside of 10.254/16, 172.16/12, 192.168/16, e.g. 10/24 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
@Uli, It's an automated dependency.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network configuration
To manage notifications about this bug go to:
I've have docker.io installed, but I didn't modify /etc/default/ubuntu-
fan nor /etc/network/fan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network
A simple docker.io installation can verify if the fix works or not.
Install an ubuntu 16.04 then install docker.io and reboot the system.
In my case it's a 16.04 with docker and kvm on the machine but I will be able
to test it only next week.
If until then no one will test I will spin up a vm for
Version 0.9.1 fixes the bug for armhf and aarch64 in the way that I
won't get an error message any more. I don't use a fan configuration so
cannot tell anything about possible side effects for (active) fan users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello Zygmunt, or anyone else affected,
Accepted ubuntu-fan into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-fan/0.9.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
** Description changed:
it seems that ubuntu-fan is causing issues with network configuration.
On 16.04 daily image:
root@localhost:~# snappy list
NameDate Version Developer
canonical-pi2 2016-02-02 3.0 canonical
canonical-pi2-lin
This bug was fixed in the package ubuntu-fan - 0.11.0
---
ubuntu-fan (0.11.0) yakkety; urgency=medium
* fanctl: fix net start/stop exit codes. (LP: #1551747)
-- Andy Whitcroft Mon, 06 Jun 2016 12:01:45 +0100
** Changed in: ubuntu-fan (Ubuntu Yakkety)
Status: In Progress
** Changed in: ubuntu-fan (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ubuntu-fan (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: ubuntu-fan (Ubuntu Xenial)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you
** Also affects: ubuntu-fan (Ubuntu Yakkety)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: In Progress
** Also affects: ubuntu-fan (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Changed in: ubuntu-fan (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
** Changed in: ubuntu-fan (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: ubuntu-fan (Ubuntu)
Importance: Undecided => High
** Changed in: snappy
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan cause
Please bump up the importance of this issue. Thanks!
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network configuration
To manage notifications
This is breaking cloud-init on AWS for us with 16.04 hvm:ebs-ssd (ami-
7a138709).
The networking.service unit goes into failed state and cloud-init
metadata crawler fails and falls back to local DataSource, skipping
provisioning of ssh keys etc.
Jun 01 19:45:07 ip-172-31-13-182 ifup[928]: bound
this looks like wlan0 was brought up just fine
seems to mostly be a cosmetic issue that /etc/network/if-up.d/ubuntu-fan doesnt
exit quietly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title
Is there a workaround?
It is anoying while working with vlans and changing networks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network configurati
** Changed in: snappy
Status: New => Confirmed
** Changed in: snappy
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-fan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
** Also affects: ubuntu-fan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network configuration
T
28 matches
Mail list logo
