Bionic currently has fping 4.0-6 and smokeping 2.6.11-4. So
unfortunately the buggy smokeping version combined with the more recent
fping version break smokeping's detection:
"FPing: WARNING: your fping binary doesn't support source address
setting (-S), I will ignore any sourceaddress configurati
** Attachment added: "4.4.0-157 test using ucf to show working behavior"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840328/+attachment/5282659/+files/4.4.0-157-working.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "strace of ucf command on 4.4.0-157"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840328/+attachment/5282661/+files/4.4.0-157-working-strace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
My xenial gate jobs began failing after the nodes began running
4.4.0-159.
The gist of this bug is that a file sitting in /posix.ini for example,
copied there by ucf from /usr/share/php7.2-common/common/posix.ini,
cannot be read by non-root users despite its permission bits b
** Attachment added: "strace of ucf command on 4.4.0-159"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840328/+attachment/5282660/+files/4.4.0-159-broken-strace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
apport information
** Tags added: apport-collected xenial
** Description changed:
My xenial gate jobs began failing after the nodes began running
4.4.0-159.
The gist of this bug is that a file sitting in /posix.ini for example,
copied there by ucf from /usr/share/php7.2-common/common/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1840328/+attachment/5282664/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840328
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1840328/+attachment/5282666/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1840328/+attachment/5282668/+files/ProcModules.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => New
--
You received this b
apport information
** Attachment added: "HookError_generic.txt"
https://bugs.launchpad.net/bugs/1840328/+attachment/5282665/+files/HookError_generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1840328/+attachment/5282667/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (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/1840328
Title:
Regression
I also confirmed that using a 'dir' backed (no overlay) LXC container
does not exhibit this broken behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840328
Title:
Regression in overlayfs betw
Hi Christian,
I have not tested the workaround yet. What I have done since I posted
this was tried to narrow it down to the specific nova commit that I
suspected triggered this. To be specific, I am deploying Newton using
OpenStack-Ansible.
OSA pulls nova directly from upstream openstack git sour
I'm having a hard time testing the workaround in #1 -- is there an
additional step necessary after modifying the abstractions/libvirt-qemu
file with the additional rule? Ie. some command to reload the file? I
restarted apparmor, libvirt-bin, and nova-compute services and it is
still failing with th
I also tested hacking in conf.script = "/bin/true" to nova. You
suspected it might fail with apparmor preventing /bin/true execution, I
can confirm that it did indeed fail.
type=AVC msg=audit(1487951915.530:99345): apparmor="DENIED" operation="exec"
profile="libvirt-5ea8f14c-73c8-4e21-9f64-28d60c
Public bug reported:
I have VMs failing to start with 2017-02-17 15:38:44.458 264015 ERROR
nova.compute.manager [instance: 0c97ab16-2d30-43fa-b0e4-a064a842b5ed]
libvirtError: internal error: process exited while connecting to
monitor: 2017-02-17T15:38:43.907222Z qemu-system-x86_64: -netdev
tap,ifn
Also thanks for the workaround suggestion. I was looking at adding a
workaround like that to the abstraction earlier but wasn't sure on the
syntax :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16656
That has been my challenge this morning in figuring this out. As far as
I know, I don't use it or need what it provides. I can't find anything
in /etc/libvirt or even /etc or my Openstack venv that is calling toward
qemu-ifup. I grepped thru /usr looking for 'qemu-ifup' and the only hits
were from
I wonder if https://review.openstack.org/#/c/425637/ has broken this on
my version of libvirt by removing the script='' entry, which is maybe
causing qemu to revert to its default of calling /etc/qemu-ifup, which
as we know is not allowed by apparmor.
--
You received this bug notification because
Sorry for the delay on getting this info.
root@ubuntu-xenial-6494:~# dpkg -l 'libvirt-bin' 'libvirt-daemon-system'
'qemu-kvm'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: upperc
Also in regard to: "Reading your Deny log again comm="qemu-system-x86".
Hmm, could it be that you run the "new" openstack against the "old" libvirt?
I see you said "with libvirt and non-openstack bits sourced from
cloud-archive", but then I'd have expected the apparmor fail against libvirt -
if a
The OpenStack change is not just in Ocata. It was also backported to
Newton. Please note the merged OpenStack patch in #4 is on branch
stable/newton. We need this fix in Newton UCA as well please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Yes it only affects the "tap" vif type.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665698
Title:
/etc/qemu-ifup not allowed by apparmor
To manage notifications about this bug go to:
https://bug
http://lists.openstack.org/pipermail/openstack-
dev/2016-December/109080.html and
https://bugs.launchpad.net/nova/+bug/1649527 contain additional info
about the bug and nova fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Looks like that is defined here:
https://github.com/openstack/nova/blob/stable/newton/nova/virt/libvirt/driver.py#L190-L208
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665698
Title:
/etc/qemu-ifu
newton and ocata are both:
MIN_LIBVIRT_VERSION = (1, 2, 1)
MIN_QEMU_VERSION = (1, 5, 3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665698
Title:
/etc/qemu-ifup not allowed by apparmor
To manage
isc-dhcp-client 4.3.3-5ubuntu12.4 fixed the problem for me.
** 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.launchpad.net/bugs/1633479
Title:
dhclie
Yep, just to confirm with the suggested workaround applied and
restarting apparmor + rebooting the system it did not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665698
Title:
/etc/qemu-ifup
I must've done something wrong when originally testing the abstraction
fix. I re-tested based on your advice and it does indeed fix the
problem. The abstraction file that I just tested, which worked, is
http://cdn.pasteraw.com/9u16uk9938mp5t3x530ok0w791nkooc.
Regarding upstream vs. packaged, I wen
@Matt, nova: Can we get some eyes on the Newton and Ocata fix you have
up? It is a pretty severe bug for me since I'm running a
vif_type=ethernet plugin with regular Ubuntu distro libvirt, so I
haven't been able to use any nova sha since early Feb due to this bug.
--
You received this bug notific
31 matches
Mail list logo