[Bug 1872281] Re: collectd python plugin not working
Is this ever going to be backported to Focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872281 Title: collectd python plugin not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1872281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826238] Re: apparmor doesn't allow to start with a non-root user
Another bug in the profile [mentioned](https://github.com/trailofbits/algo/pull/1405#issuecomment-487079035) by @demyers Apr 26 13:53:37 vpn5 kernel: audit: type=1107 audit(1556286817.984:33): pid=766 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=849 label="/usr/lib/ipsec/charon" peer_pid=1 peer_label="unconfined" Apr 26 13:53:37 vpn5 audit[766]: USER_AVC pid=766 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=849 label="/usr/lib/ipsec/charon" peer_pid=1 peer_label="unconfined" This call to dbus needs to be allowed as well. Should I file another issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826238 Title: apparmor doesn't allow to start with a non-root user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1826238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826238] Re: apparmor doesn't allow to start with a non-root user
** Description changed:
Hello,
I'm using 19.04 (Disco Dingo), kernel: 5.0.0-13-generic amd64
packages:
ii libcharon-standard-plugins 5.7.1-1ubuntu2
ii libstrongswan 5.7.1-1ubuntu2
ii libstrongswan-standard-plugins 5.7.1-1ubuntu2
ii strongswan 5.7.1-1ubuntu2
ii strongswan-charon 5.7.1-1ubuntu2
ii strongswan-libcharon 5.7.1-1ubuntu2
ii strongswan-starter 5.7.1-1ubuntu2
/etc/strongswan.conf - https://pastebin.com/gwPfedeS
strongswan error:
Apr 24 15:47:23 ubuntu-1904-2 ipsec[1422]: 00[LIB] dropping capabilities
failed: Operation not permitted
Apr 24 15:47:23 ubuntu-1904-2 ipsec[1422]: 00[DMN] capability dropping failed
- aborting charon
strongswan logs - https://pastebin.com/VeqBewZx
- starter charon - https://pastebin.com/QNYPGSN8
+ strace charon - https://pastebin.com/QNYPGSN8
capset({version=_LINUX_CAPABILITY_VERSION_3, pid=0},
{effective=1
[Bug 1826238] Re: apparmor doesn't allow to start with a non-root user
CAP_SETPCAP should be allowed in the profile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826238 Title: apparmor doesn't allow to start with a non-root user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1826238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826238] [NEW] apparmor doesn't allow to start with a non-root user
Public bug reported:
Hello,
I'm using 19.04 (Disco Dingo), kernel: 5.0.0-13-generic amd64
packages:
ii libcharon-standard-plugins 5.7.1-1ubuntu2
ii libstrongswan 5.7.1-1ubuntu2
ii libstrongswan-standard-plugins 5.7.1-1ubuntu2
ii strongswan 5.7.1-1ubuntu2
ii strongswan-charon 5.7.1-1ubuntu2
ii strongswan-libcharon 5.7.1-1ubuntu2
ii strongswan-starter 5.7.1-1ubuntu2
/etc/strongswan.conf - https://pastebin.com/gwPfedeS
strongswan error:
Apr 24 15:47:23 ubuntu-1904-2 ipsec[1422]: 00[LIB] dropping capabilities
failed: Operation not permitted
Apr 24 15:47:23 ubuntu-1904-2 ipsec[1422]: 00[DMN] capability dropping failed -
aborting charon
strongswan logs - https://pastebin.com/VeqBewZx
starter charon - https://pastebin.com/QNYPGSN8
capset({version=_LINUX_CAPABILITY_VERSION_3, pid=0},
{effective=1
[Bug 1748894] Re: intermittent dhcp failures
Same problem here, running Queens. DHCP packets are going out, but not reaching the server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748894 Title: intermittent dhcp failures To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1748894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787604] Re: Cluster stuck in CREATE_IN_PROGRESS while Heat shows CREATE_COMPLETE
Hi Rick, Thanks for your reply! Do you know where it was fixed? Might be a bug number or a commit message. Thanks you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787604 Title: Cluster stuck in CREATE_IN_PROGRESS while Heat shows CREATE_COMPLETE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1787604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787604] [NEW] Cluster stuck in CREATE_IN_PROGRESS while Heat shows CREATE_COMPLETE
Public bug reported: For some reason I can't create clusters in Queens. Clusters just stuck in CREATE_IN_PROGRESS, but Heat status is CREATE_COMPLETE. THe problem is floating, sometimes It becomes CREATE_COMPLETE, but sometimes hangs on CREATE_IN_PROGRESS for forever. python-magnum-6.1.1-1002.el7.noarch python2-magnumclient-2.9.1-1.el7.noarch openstack-magnum-api-6.1.1-1002.el7.noarch openstack-magnum-conductor-6.1.1-1002.el7.noarch openstack-magnum-common-6.1.1-1002.el7.noarch openstack-magnum-ui-4.0.0-1.el7.noarch openstack coe cluster show - http://paste.openstack.org/show/728313/ openstack stack show - http://paste.openstack.org/show/728314/ magnum.conf - http://paste.openstack.org/show/728315/ no errors in logs. Is this a bug? How to debug it? ** Affects: magnum (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/1787604 Title: Cluster stuck in CREATE_IN_PROGRESS while Heat shows CREATE_COMPLETE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1787604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582585] Re: the speed of query user from ldap server is very slow
I have the same issue on Ocata (keystone-11.0.3), each request to keystone takes 15-20 sec. There are more then 15 records in the id_mapping table. Does the patch actually fix the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582585 Title: the speed of query user from ldap server is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1582585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
