[Bug 1779674] Re: AppArmor does not permit access to rbd admin socket hardcoded in OpenStack charms
What is the consequence of this access being denied? Is this admin socket something used by the charm, or admins logging in on the node? ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1779674 Title: AppArmor does not permit access to rbd admin socket hardcoded in OpenStack charms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1779674/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779621] Re: chrony exits unexpectedly
Can you show the resulting /etc/chrony/chrony.conf file?
Also, my puppet-foo is rusty, but doesn't this mean all 3 packages will
be installed alongside chrony:
package {"chrony":
ensure => present,
require => Package['openntpd', 'ntpdate', 'ntp'],
}
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to chrony in Ubuntu.
https://bugs.launchpad.net/bugs/1779621
Title:
chrony exits unexpectedly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779621] Re: chrony exits unexpectedly
If you have disabled stepping, maybe chrony gives up trying to adjust the clock when you come back from suspend and the clock is incorrect. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to chrony in Ubuntu. https://bugs.launchpad.net/bugs/1779621 Title: chrony exits unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779621] Re: chrony exits unexpectedly
While I try to reproduce this, could you please attach the custom config you said you have for chronyd, and where it is located exactly? systemd overrides, config file, etc ** Changed in: chrony (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to chrony in Ubuntu. https://bugs.launchpad.net/bugs/1779621 Title: chrony exits unexpectedly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779686] Re: package apache2 2.4.29-1ubuntu4.2 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1
Thanks for filing this bug in Ubuntu. This is the error reported in the logs: info: Executing deferred 'a2enconf apache2-doc' for package apache2-doc ERROR: Conf apache2-doc does not exist! dpkg: error processing package apache2 (--configure): installed apache2 package post-installation script subprocess returned error exit status 1 Could you please check if you have these files: ls -la /etc/apache2/conf-available/apache2-doc.conf /etc/apache2/conf- enabled/apache2-doc.conf This is what I get on a system where I installed apache2-doc: root@bionic-apache2doc:~# ls -la /etc/apache2/conf-available/apache2-doc.conf /etc/apache2/conf-enabled/apache2-doc.conf -rw-r--r-- 1 root root 221 Oct 23 2017 /etc/apache2/conf-available/apache2-doc.conf lrwxrwxrwx 1 root root 34 Jul 3 18:07 /etc/apache2/conf-enabled/apache2-doc.conf -> ../conf-available/apache2-doc.conf The file installed in conf-available is part of the apache2-doc package, and it is enabled via a command like this in the post-installation step: a2enconf apache2-doc I just did a fresh install of 2.4.29-1ubuntu4.1 and upgraded it to 2.4.29-1ubuntu4.2, and it went just fine, so let's see if we can find what's different on your system. ** Changed in: apache2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1779686 Title: package apache2 2.4.29-1ubuntu4.2 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1779686/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1779753] Re: on both my home and work pc, problems with apache2 package and apt
Thanks for filing this bug in Ubuntu. Please attach the following information: - output of "sudo apt update && sudo apt -f install" - output of "dpkg -l|grep apache" - apt-cache policy apache2 The logs show just bits and pieces of what looks like failed downloads. ** Changed in: apache2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1779753 Title: on both my home and work pc, problems with apache2 package and apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1779753/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
I've uploaded new versions of keepalived to cosmic, bionic (awaiting SRU team review), pike-staging, and ocata-staging. I need to confirm with other cloud archive admins that this is ok to backport to pike/ocata cloud archives prior to promoting to pike-proposed/ocata-proposed. In the mean time if you'd like to test the ocata fix (where this was initially reported) you can install from the staging PPA: sudo add-apt-repository ppa:ubuntu-cloud-archive/ocata-staging sudo apt update And from pike: sudo add-apt-repository ppa:ubuntu-cloud-archive/pike-staging sudo apt update -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
Moving back to New for neutron for the time being since we think this may be fixed in keepalived. ** Description changed: + [Impact] + This is the same issue reported in https://bugs.launchpad.net/neutron/+bug/1731595, however that is marked as 'Fix Released' and the issue is still occurring and I can't change back to 'New' so it seems best to just open a new bug. It seems as if this bug surfaces due to load issues. While the fix - provided by Venkata (https://review.openstack.org/#/c/522641/) should - help clean things up at the time of l3 agent restart, issues seem to - come back later down the line in some circumstances. xavpaice mentioned - he saw multiple routers active at the same time when they had 464 - routers configured on 3 neutron gateway hosts using L3HA, and each - router was scheduled to all 3 hosts. However, jhebden mentions that - things seem stable at the 400 L3HA router mark, and it's worth noting - this is the same deployment that xavpaice was referring to. + provided by Venkata in https://bugs.launchpad.net/neutron/+bug/1731595 + (https://review.openstack.org/#/c/522641/) should help clean things up + at the time of l3 agent restart, issues seem to come back later down the + line in some circumstances. xavpaice mentioned he saw multiple routers + active at the same time when they had 464 routers configured on 3 + neutron gateway hosts using L3HA, and each router was scheduled to all 3 + hosts. However, jhebden mentions that things seem stable at the 400 L3HA + router mark, and it's worth noting this is the same deployment that + xavpaice was referring to. - It seems to me that something is being pushed to it's limit, and - possibly once that limit is hit, master router advertisements aren't - being received, causing a new master to be elected. If this is the case - it would be great to get to the bottom of what resource is getting - constrained. + keepalived has a patch upstream in 1.4.0 that provides a fix for + removing left-over addresses if keepalived aborts. That patch will be + cherry-picked to Ubuntu keepalived packages. + + [Test Case] + The following SRU process will be followed: + https://wiki.ubuntu.com/OpenStackUpdates + + In order to avoid regression of existing consumers, the OpenStack team + will run their continuous integration test against the packages that are + in -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. + + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. + + [Regression Potential] + The regression potential is lowered as the fix is cherry-picked without change from upstream. In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. + + [Discussion] ** Changed in: neutron (Ubuntu) Status: Triaged => New ** Changed in: neutron (Ubuntu) Importance: High => Undecided ** Changed in: neutron (Ubuntu Xenial) Importance: High => Undecided ** Changed in: neutron (Ubuntu Xenial) Status: Triaged => New ** Changed in: neutron (Ubuntu Bionic) Importance: High => Undecided ** Changed in: neutron (Ubuntu Bionic) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
** Summary changed: - L3 HA: multiple agents are active at the same time + [SRU] L3 HA: multiple agents are active at the same time -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: L3 HA: multiple agents are active at the same time
It appears the following commits are required to fix this for keepalived: commit e90a633c34fbe6ebbb891aa98bf29ce579b8b45c Author: Quentin Armitage Date: Fri Dec 15 21:14:24 2017 + Fix removing left-over addresses if keepalived aborts Issue #718 reported that if keepalived terminates abnormally when it has vrrp instances in master state, it doesn't remove the left-over VIPs and eVIPs when it restarts. This is despite commit f4c10426c saying that it resolved this problem. It turns out that commit f4c10426c did resolve the problem for VIPs or eVIPs, although it did resolve the issue for iptables and ipset configuration. This commit now really resolves the problem, and residual VIPs and eVIPs are removed at startup. Signed-off-by: Quentin Armitage commit f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 Author: Quentin Armitage Date: Sun Mar 6 09:53:27 2016 + Remove ip addresses left over from previous failure If keepalived terminates unexpectedly, for any instances for which it was master, it leaves ip addresses configured on the interfaces. When keepalived restarts, if it starts in backup mode, the addresses must be removed. In addition, any iptables/ipsets entries added for !accept_mode must also be removed, in order to avoid multiple entries being created in iptables. This commit removes any addresses and iptables/ipsets configuration for any interfaces that exist when iptables starts up. If keepalived shut down cleanly, that will only be for non-vmac interfaces, but if it terminated unexpectedly, it can also be for any left-over vmacs. Signed-off-by: Quentin Armitage f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 is already included in: * keepalived 1:1.3.9-1build1 (bionic/queens, cosmic/rocky) * keepalived 1:1.3.2-1build1 (artful/pike) * keepalived 1:1.3.2-1 (zesty/ocata) [1] [1] zesty is EOL - https://launchpad.net/ubuntu/+source/keepalived/1:1.3.2-1 f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 is not included in: * keepalived 1:1.2.19-1ubuntu0.2 (xenial/mitaka) The backport of f4c10426ca0a7c3392422c22079f1b71e7d4ebe9 to xenial does not look trivial. I'd prefer to backport keepalived 1:1.3.2-* to the pike/ocata cloud archives. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744062] Re: L3 HA: multiple agents are active at the same time
As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595: "Comment for the folks that are noticing this as 'fix released' but still affected - see https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c for the rest of this fix, we need keepalived to be at least 1.4.0 in order to have this commit." I just checked and the patch Xav referenced can be backported fairly cleanly to at least keepalived 1:1.2.19-1 (xenial/mitaka) and above. ** Also affects: keepalived (Ubuntu) Importance: Undecided Status: New ** No longer affects: keepalived (Ubuntu Artful) ** Changed in: keepalived (Ubuntu) Importance: Undecided => High ** Changed in: keepalived (Ubuntu) Status: New => Triaged ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Bionic) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Bionic) Status: New => Triaged ** No longer affects: cloud-archive/newton ** No longer affects: neutron (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1744062 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
Since this bug is already marked as fix released for the cloud-archive, let's please track this issue in the following bug: https://bugs.launchpad.net/ubuntu/+bug/1744062 ** No longer affects: keepalived (Ubuntu) ** No longer affects: keepalived (Ubuntu Xenial) ** No longer affects: keepalived (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
Xav, I just checked and the patch you referenced can be backported fairly cleanly to at least keepalived 1:1.2.19-1 (xenial/mitaka) and above. ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Bionic) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Bionic) Status: New => Triaged ** Changed in: keepalived (Ubuntu) Status: New => Triaged ** Changed in: keepalived (Ubuntu) Importance: Undecided => High ** Changed in: keepalived (Ubuntu Xenial) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
** No longer affects: keepalived (Ubuntu Zesty) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1731595] Re: L3 HA: multiple agents are active at the same time
** Also affects: keepalived (Ubuntu) Importance: Undecided Status: New ** No longer affects: keepalived (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1731595 Title: L3 HA: multiple agents are active at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1731595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
