[Bug 1768914] Re: package apache2 2.4.29-1ubuntu4.1 failed to install/upgrade: installed apache2 package post-installation script subprocess returned error exit status 1
When you switch an expired (previously incomplete) bug back to new, you have to provide additional information. You didn't even answer my question from comment #3. Also, it looks like the reporter deleted a lot of files: modified.conffile..etc.apache2.mods-available.reqtimeout.load: [deleted] Including the one we are talking about. ** 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/1768914 Title: package apache2 2.4.29-1ubuntu4.1 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/1768914/+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 1778456] Re: Panic in gencache_stabilize
It's difficult to do anything about this without the crash file, or steps to reproduce it. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1778456 Title: Panic in gencache_stabilize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1778456/+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 1788499] Re: xen crashes on system resume
@smb, do you have any idea about this? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to xen in Ubuntu. https://bugs.launchpad.net/bugs/1788499 Title: xen crashes on system resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1788499/+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 1789097] Re: winbind does not work after reboot on Mint 19 / Ubuntu 18.04
Thanks for filing this bug in Ubuntu. What do you mean by "does not work", exactly? Doesn't the network come up eventually? Or is this a desktop machine where the network is wireless and only available after someone logs in? Please show exactly what is not working, your configuration files, and also please provide logs. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1789097 Title: winbind does not work after reboot on Mint 19 / Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789097/+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 1788340] Re: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1731502 *** https://bugs.launchpad.net/bugs/1731502 Thanks for filing this bug in Ubuntu. This bug is a duplicate of #1731502, where samba is installed on a machine which is not a server and has no network connectivity before someone logs in. Typically this is a wifi network that is only available after login. I suggest you run this after logging in and making sure the network is available: sudo apt update sudo apt -f install ** This bug has been marked a duplicate of bug 1731502 nmbd starts fine with no interfaces, but doesn't notify systemd that it started -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1788340 Title: package samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1788340/+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 1788776] Re: Ubuntu 18.04 samba/samb-vfs-module not compiled/built --with-acl-support or zfsacl vfs module
Marking as wishlist since it's a new feature for a stable release. ** Changed in: samba (Ubuntu) Importance: Undecided => Wishlist ** Changed in: samba (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1788776 Title: Ubuntu 18.04 samba/samb-vfs-module not compiled/built --with-acl- support or zfsacl vfs module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1788776/+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 1788986] Re: Quagga not starting when using vtysh integrated configuration
Thanks for filing this bug in Ubuntu. I'm not familiar with quagga, sorry, so could you please elaborate on why is this a bug? Did you add a configuration directive and as a result the daemon stopped working? What was your configuration in whatever you were running before bionic (you didn't say which ubuntu release you were on)? ** Changed in: quagga (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to quagga in Ubuntu. https://bugs.launchpad.net/bugs/1788986 Title: Quagga not starting when using vtysh integrated configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/1788986/+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 1789078] Re: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess installed mysql-server-5.7 package post-installation script gab den Fehler-Ausgangsstatus 127
Thanks for filing this bug in Ubuntu. I don't know what you did, but somehow you ended up missing an important file: /var/lib/dpkg/info/mysql-server-5.7.postinst: Zeile 191: /usr/share/mysql-common/configure-symlinks: Datei oder Verzeichnis nicht gefunden [1mdpkg:[0m Fehler beim Bearbeiten des Paketes mysql-server-5.7 (--configure): Unterprozess installed mysql-server-5.7 package post-installation script gab den Fehler-Ausgangsstatus 127 zurück That file (configure-symlinks) is part of the mysql-common package. I suggest you try to install, or reinstall, it. Something like: sudo apt update sudo apt install mysql-common or sudo apt install --reinstall mysql-common and finally sudo apt -f install Other than that, there isn't much else that can be suggested because there is no clear indication of a bug here, with steps to reproduce it, just a support request. ** Changed in: mysql-5.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-5.7 in Ubuntu. Matching subscriptions: main https://bugs.launchpad.net/bugs/1789078 Title: package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess installed mysql-server-5.7 package post- installation script gab den Fehler-Ausgangsstatus 127 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1789078/+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 1583324] Re: Samba won't start when an include statement in smb.conf has a variable substitution
Trusty verification Starting with the packages that show the bug: ubuntu@trusty-samba-include-1583324:~$ apt-cache policy samba samba: Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.16 Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.16 Version table: *** 2:4.3.11+dfsg-0ubuntu0.14.04.16 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status ubuntu@trusty-samba-include-1583324:~$ sudo samba-tool testparm -d 2 lpcfg_load: refreshing parameters from /etc/samba/smb.conf Can't find include file /etc/samba/smb.conf.%U ERROR: Unable to load default file ubuntu@trusty-samba-include-1583324:~$ echo $? 255 Upgrading to the packages from proposed: ubuntu@trusty-samba-include-1583324:~$ apt-cache policy samba samba: Installed: 2:4.3.11+dfsg-0ubuntu0.14.04.17 Candidate: 2:4.3.11+dfsg-0ubuntu0.14.04.17 Version table: *** 2:4.3.11+dfsg-0ubuntu0.14.04.17 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status The testparm command now works. It shows the config file, remarks that the "%U" file was ignored, and exits with status 0: ubuntu@trusty-samba-include-1583324:~$ sudo samba-tool testparm -d 2 lpcfg_load: refreshing parameters from /etc/samba/smb.conf Tried to load /etc/samba/smb.conf.%U but variable substitution in filename, ignoring file. Press enter to see a dump of your service definitions # Global parameters [global] netbios name = SAMBA server string = %h server (Samba, Ubuntu) map to guest = Bad User obey pam restrictions = Yes pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes log level = 2 log file = /var/log/samba/log.%m max log size = 1000 usershare allow guests = Yes panic action = /usr/share/samba/panic-action %d idmap config * : backend = tdb include = /etc/samba/smb.conf.%U ubuntu@trusty-samba-include-1583324:~$ echo $? 0 Trusty verification complete. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- 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/1583324 Title: Samba won't start when an include statement in smb.conf has a variable substitution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1583324/+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 1750356] Re: Apache2: BalancerMember worker hostname (65.character.host.name) too long
Bionic verification. Starting with the packages that show the bug: ubuntu@bionic-apache-1750356:~$ apt-cache policy apache2 apache2: Installed: 2.4.29-1ubuntu4.2 Candidate: 2.4.29-1ubuntu4.2 Version table: *** 2.4.29-1ubuntu4.2 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status status shows the expected error: (...) Aug 28 17:20:37 bionic-apache-1750356 systemd[1]: Starting The Apache HTTP Server... Aug 28 17:20:37 bionic-apache-1750356 apachectl[2040]: AH00526: Syntax error on line 24 of /etc/apache2/sites-enabled/000-default.conf: Aug 28 17:20:37 bionic-apache-1750356 apachectl[2040]: BalancerMember worker hostname (xx-xx--x-x.xx--x.x-xxx.xxx.x.) too long Aug 28 17:20:37 bionic-apache-1750356 apachectl[2040]: Action 'start' failed. Upgrading to the packages in proposed: ubuntu@bionic-apache-1750356:~$ apt-cache policy apache2 apache2: Installed: 2.4.29-1ubuntu4.3 Candidate: 2.4.29-1ubuntu4.3 Version table: *** 2.4.29-1ubuntu4.3 500 500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4.2 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages Service is running right after the upgrade: ubuntu@bionic-apache-1750356:~$ sudo systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: active (running) since Tue 2018-08-28 17:22:31 UTC; 25s ago Main PID: 2847 (apache2) Tasks: 54 (limit: 4915) CGroup: /system.slice/apache2.service ├─2847 /usr/sbin/apache2 -k start ├─2849 /usr/sbin/apache2 -k start └─2850 /usr/sbin/apache2 -k start Aug 28 17:22:31 bionic-apache-1750356 systemd[1]: Starting The Apache HTTP Server... Aug 28 17:22:31 bionic-apache-1750356 systemd[1]: Started The Apache HTTP Server. Accessing the balancer url triggers the expected error: ubuntu@bionic-apache-1750356:~$ wget http://localhost/foo --2018-08-28 17:23:34-- http://localhost/foo Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 502 Proxy Error 2018-08-28 17:23:35 ERROR 502: Proxy Error. And the logs confirm that the server tried to reach the balancer member: ubuntu@bionic-apache-1750356:~$ tail /var/log/apache2/error.log -n 1 [Tue Aug 28 17:23:35.277191 2018] [proxy:error] [pid 2850:tid 139871414892288] [client 127.0.0.1:49520] AH00898: DNS lookup failure for: xx-xx--x-x.xx--x.x-xxx.xxx.x. returned by /foo Verification complete and successfull for bionic. ** Description changed: [Impact] If the BalancerMember directive contains a URL with a hostname longer than X characters, apache2 will fail to start with the following error: BalancerMember worker hostname (65.character.host.name) too long RFC1035 allows for longer hostnames, and apache upstream has this fix already. [Test Case] * Install the packages: - sudo apt install apache + sudo apt install apache2 * Edit /etc/apache2/sites-available/000-default.conf and add the following block inside the VirtualHost block: BalancerMember "http://xx-xx--x-x.xx--x.x-xxx.xxx.x.:90/; BalancerMember "http://xx-xx--x-x.xx--x.x-xxx.xxx.x.:91/; ProxyRequests Off Order deny,allow Allow from all RewriteEngine On RewriteRule ^/foo balancer://test/foo [P,L] * Enable the necessary apache modules: sudo a2enmod proxy_balancer proxy lbmethod_byrequests proxy_http rewrite * Restart apache2, which will fail: sudo systemctl restart apache2 * Run the status action and expect an error like this: sudo systemctl status apache2.service ... Jun 27 18:31:16 bionic-apache-1750356 apachectl[2218]: BalancerMember worker hostname (xx-xx--x-x.xx--x.x-xxx.xxx.x.) too long * Update the apache2 packages to the ones available in proposed. As part of the upgrade, apache2 will be restarted again, and in this time it will work. Confirm with systemctl status apache2 that there are no errors this time: sudo systemctl status apache2 * Try to access http://localhost/foo to trigger the load balancer configuration. It will trigger a DNS error as we don't have an entry for the BalancerMember hostname, but it shows that the configuration worked: ubuntu@bionic-apache-1750356:~$ wget http://localhost/foo --2018-06-27 18:39:58-- http://localhost/foo Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:80... connected. HTTP request
[Bug 1788983] Re: package mysql-server-5.7 5.7.23-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. No idea what happened: 2018-08-25T04:40:38.044455Z 4 [ERROR] InnoDB: Operating system error number 17 in a file operation. 2018-08-25T04:40:38.044493Z 4 [ERROR] InnoDB: Error number 17 means 'File exists' 2018-08-25T04:40:38.044505Z 4 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html 2018-08-25T04:40:38.044515Z 4 [ERROR] InnoDB: Cannot create file './mysql/innodb_table_stats.ibd' 2018-08-25T04:40:38.044525Z 4 [ERROR] InnoDB: The file './mysql/innodb_table_stats.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './mysql/innodb_table_stats.ibd' under the 'datadir' of MySQL. 2018-08-25T04:41:14.564124Z 6 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found. 2018-08-25T04:41:14.564157Z 6 [ERROR] InnoDB: Fetch of persistent statistics requested for table `badincdailylogs2018`.`important_info` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. 2018-08-25T04:46:12.616491Z 61 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found. 2018-08-25T04:46:12.616538Z 61 [ERROR] InnoDB: Fetch of persistent statistics requested for table `blueclub-insight`.`tbl_admin_user` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. 2018-08-25T04:46:12.631123Z 61 [ERROR] InnoDB: Table `mysql`.`innodb_table_stats` not found. 2018-08-25T04:46:12.631159Z 61 [ERROR] InnoDB: Fetch of persistent statistics requested for table `blueclub-insight`.`tbl_log_admin` but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. Maybe different directories were specified, and that broke the mysql upgrade script? ** Changed in: mysql-5.7 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-5.7 in Ubuntu. Matching subscriptions: main https://bugs.launchpad.net/bugs/1788983 Title: package mysql-server-5.7 5.7.23-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1788983/+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 1010625] Re: named logs are not being reported in logwatch
Indeed, the configuration we have in /usr/share/logwatch/dist.conf (which overrides /usr/share/logwatch/default.conf) seems correct and no longer uses "messages". ** Changed in: logwatch (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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 1788856] Re: multipathd: uevent trigger error
Could you please attach the relevant logs? Please run this command on the affected machine: apport-collect -p multipath-tools 1788856 ** Changed in: multipath-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1788856 Title: multipathd: uevent trigger error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1788856/+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 1787886] Re: Upgrade from 16LTS to 18LTS breaks Apache2
The php release upgrade is a bit odd indeed, or so I think. If you have the versioned packages installed only (like php7.0-curl without php- curl), then the release upgrade might not update those packages, and even remove some. One should always pay close attention to what the release upgrade tool is telling you when it gives a summary of the actions it is going to take. I'm not familiar with php packaging, so I don't know if this is a known issue or not. -- 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/1787886 Title: Upgrade from 16LTS to 18LTS breaks Apache2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1787886/+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 1787886] Re: Upgrade from 16LTS to 18LTS breaks Apache2
Resseting to new as logs were provided. ** Changed in: apache2 (Ubuntu) Status: Incomplete => New -- 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/1787886 Title: Upgrade from 16LTS to 18LTS breaks Apache2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1787886/+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 1789045] Re: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches
Hi again Slawek, Just for some further details, the new versions of keepalived came about due to: https://bugs.launchpad.net/cloud-archive/+bug/1744062. In particular, see https://bugs.launchpad.net/cloud-archive/+bug/1744062/comments/14 for the descriptions of the commits that are included to fix that bug - essentially the fixes cleanup unused ip addresses on startup. The same fixes are in the bionic version of keepalived. Thanks, Corey -- 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/1789045 Title: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045/+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 1789045] Re: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches
Slawek, Thank you for reporting this issue. The new keepalived versions include a cherry-pick of https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c. I'm currently building a new xenial version of keepalived in a PPA for testing purposes with this patch removed. Would you be able to re-run tests with it to see if this fixes the issue? You can get the fix by running the following commands on a xenial machine. You'll need to use mitaka (base xenial without cloud archive) or use the ocata or pike cloud archives. sudo add-apt-repository ppa:corey.bryant/xenial-bug-1789045 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/1789045 Title: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045/+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 1789045] Re: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches
Slawek, for stable/queens, can you confirm the version of keepalived that your tests are running with? The queens cloud archive has keepalived 1:1.3.9-1ubuntu0.18.04.1~cloud0, however I'm wondering if you're running with the base xenial version of 1:1.2.24-1ubuntu0.16.04.1. -- 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/1789045 Title: keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable branches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1789045/+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
