[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Seems like Ubuntu 16.04 (release date 2016-04-21) will have irqbalance 1.0.9-1. It is still the old one for 15.10. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+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 1247107] Re: Runaway irqbalance consuming CPU and Memory
Raspberry updated to 15.10 Ubuntu Mate and 480 MB memory lost in irqbalance. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+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 1512079] [NEW] package php5-common (not installed) failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10
Public bug reported: package php5-common (not installed) failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: php5-common (not installed) ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 Date: Sun Nov 1 15:53:32 2015 DuplicateSignature: package:php5-common:(not installed):子进程 已安装 post-installation 脚本 返回错误状态 10 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 10 InstallationDate: Installed on 2015-09-20 (41 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: php5 Title: package php5-common (not installed) failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1512079 Title: package php5-common (not installed) failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1512079/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Also problem in 15.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1512112] [NEW] add manpage for pear
Public bug reported: Currently help is only available from `pear help`. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: php-pear 5.6.11+dfsg-1ubuntu3.1 Uname: Linux 4.2.5-040205-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl fglrx ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Sun Nov 1 17:03:33 2015 InstallationDate: Installed on 2015-04-20 (195 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: php5 UpgradeStatus: Upgraded to wily on 2015-10-26 (6 days ago) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1512112 Title: add manpage for pear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1512112/+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 1177432] Re: Enable backports in cloud-init archive template
Just ran into this issue again today when testing the LXD backport. This is pretty annoying as it's causing a completely different user experience for cloud users compared to regular distro users. Also, at least in trusty, apt-add-repository doesn't know how to add backports, so a user will need to manually update /etc/apt/sources.list and then run apt-get update which makes installing backports significantly harder than it should be. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1177432 Title: Enable backports in cloud-init archive template To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1177432/+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 1512178] [NEW] after upgrade to mysql-5.6 database stopped working
Public bug reported: my former running mysql-5.5 database stopped working after the upgrade. what can I do? root@server:~# service mysql start start: Job failed to start root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty root@server:~# apt-cache policy mysql-server-5.6 mysql-server-5.6: Installiert: 5.6.27-0ubuntu0.14.04.1 Installationskandidat: 5.6.27-0ubuntu0.14.04.1 Versionstabelle: *** 5.6.27-0ubuntu0.14.04.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 5.6.16-1~exp1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages tail -f /var/log/mysql/mysql.log /var/log/mysql/error.log ==> /var/log/mysql/mysql.log <== ==> /var/log/mysql/error.log <== 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'CSV' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'MEMORY' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'MRG_MYISAM' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'MyISAM' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'sha256_password' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'mysql_old_password' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'mysql_native_password' 2015-11-01 23:51:04 1457 [Note] Shutting down plugin 'binlog' 2015-11-01 23:51:04 1457 [Note] /usr/sbin/mysqld: Shutdown complete 2015-11-01 23:54:49 2827 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2015-11-01 23:54:49 2827 [Note] Plugin 'FEDERATED' is disabled. /usr/sbin/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13 - Permission denied) 2015-11-01 23:54:49 2827 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2015-11-01 23:54:49 2827 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-11-01 23:54:49 2827 [Note] InnoDB: The InnoDB memory heap is disabled 2015-11-01 23:54:49 2827 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-11-01 23:54:49 2827 [Note] InnoDB: Memory barrier is not used 2015-11-01 23:54:49 2827 [Note] InnoDB: Compressed tables use zlib 1.2.8 2015-11-01 23:54:49 2827 [Note] InnoDB: Using Linux native AIO 2015-11-01 23:54:49 2827 [Note] InnoDB: Not using CPU crc32 instructions 2015-11-01 23:54:49 2827 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-11-01 23:54:49 2827 [Note] InnoDB: Completed initialization of buffer pool 2015-11-01 23:54:49 2827 [ERROR] InnoDB: ./ibdata1 can't be opened in read-write mode 2015-11-01 23:54:49 2827 [ERROR] InnoDB: The system tablespace must be writable! 2015-11-01 23:54:49 2827 [ERROR] Plugin 'InnoDB' init function returned error. 2015-11-01 23:54:49 2827 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2015-11-01 23:54:49 2827 [ERROR] Unknown/unsupported storage engine: InnoDB 2015-11-01 23:54:49 2827 [ERROR] Aborting 2015-11-01 23:54:49 2827 [Note] Binlog end 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'partition' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'BLACKHOLE' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'ARCHIVE' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_METRICS' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2015-11-01 23:54:49 2827 [Note] Shutting down plugin
[Bug 1512131] [NEW] Apparmor complains about multiple /run/dovecot file access
Public bug reported: Hi, since I upgraded from XUbuntu 15.04 to 15.10 I started to get a lot of apparmor complains about dovecot. The complains were more or less like this: operation="connect" profile="/usr/lib/dovecot/auth" name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 operation="connect" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-worker" comm="auth" requested_mask="wr" denied_mask="wr" fsuid=117 ouid=117 operation="file_perm" profile="/usr/lib/dovecot/anvil" name="/run/dovecot/anvil-auth-penalty" comm="anvil" requested_mask="r" denied_mask="r" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/anvil" name="/run/dovecot/anvil" comm="anvil" requested_mask="r" denied_mask="r" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/anvil" name="/run/dovecot/anvil" comm="anvil" requested_mask="w" denied_mask="w" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-master" comm="auth" requested_mask="w" denied_mask="w" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-worker" comm="auth" requested_mask="r" denied_mask="r" fsuid=0 ouid=117 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/auth-worker" comm="auth" requested_mask="w" denied_mask="w" fsuid=117 ouid=117 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/login/login" comm="auth" requested_mask="r" denied_mask="r" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/auth" name="/run/dovecot/login/login" comm="auth" requested_mask="w" denied_mask="w" fsuid=117 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/imap" name="/run/dovecot/login/imap" comm="imap" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/imap" name="/run/dovecot/login/imap" comm="imap" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 operation="file_perm" profile="/usr/lib/dovecot/ssl-params" name="/run/dovecot/login/ssl-params" comm="ssl-params" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 operation="file_receive" profile="/usr/lib/dovecot/imap" comm="imap" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/imap-login" operation="file_receive" profile="/usr/lib/dovecot/imap-login" comm="imap" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/imap" operation="signal" profile="/usr/sbin/dovecot" comm="dovecot" requested_mask="send" denied_mask="send" signal=int peer="/usr/lib/dovecot/auth" To avoid them, I added some stuff to the /etc/apparmor.d/local directory, patch attached. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dovecot-core 1:2.2.18-2ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 1 19:42:56 2015 InstallationDate: Installed on 2012-11-11 (1085 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: dovecot UpgradeStatus: Upgraded to wily on 2015-11-01 (0 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Patch added: "Patch for local files" https://bugs.launchpad.net/bugs/1512131/+attachment/4510551/+files/patch ** Patch removed: "Patch for local files" https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1512131/+attachment/4510551/+files/patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1512131 Title: Apparmor complains about multiple /run/dovecot file access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1512131/+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 1512131] Re: Apparmor complains about multiple /run/dovecot file access
** Attachment added: "Patch for local files" https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1512131/+attachment/4510556/+files/patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1512131 Title: Apparmor complains about multiple /run/dovecot file access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1512131/+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 1512185] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510819/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510815/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510811/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510821/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
apport information
** Also affects: linux-meta-lts-vivid (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected trusty uec-images
** Description changed:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
- I'm also not sure if this is related to LP:1505564, which is for
- amd64/x86_64.
+ I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
+ crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.18
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ Package: qemu (not installed)
+ PciMultimedia:
+
+ ProcEnviron:
+ TERM=xterm
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_GB
+ SHELL=/bin/bash
+ ProcFB:
+
+ ProcKernelCmdLine: console=ttyS0,9600n8r ro
+ ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: trusty uec-images trusty uec-images
+ Uname: Linux 3.19.0-31-generic aarch64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm
+ _MarkForUpload: True
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510810/+files/BootDmesg.txt
--
You
[Bug 1512185] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510814/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510816/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510817/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510818/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] KvmCmdLine.txt
apport information ** Attachment added: "KvmCmdLine.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510813/+files/KvmCmdLine.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510820/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510812/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512131] Re: Apparmor complains about multiple /run/dovecot file access
The attachment "Patch for local files" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1512131 Title: Apparmor complains about multiple /run/dovecot file access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1512131/+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 1512168] [NEW] package ntp 1:4.2.6.p5+dfsg-3ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: en français : probléme logiciel detecté ProblemType: Package DistroRelease: Ubuntu 15.10 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Sun Nov 1 15:38:07 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2014-07-16 (473 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=065236d8-7c3b-4ece-928d-db38e2f77c96 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: Upgraded to wily on 2015-10-23 (9 days ago) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1512168 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1512168/+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 1510565] Re: [needs-packaging] Juju 1.25.0 is not in xenial and wily
I certify that juju 1.25.0 is suitable for local charm development and testing using both trusty and wily containers. Users of wily juju 1.25.0 can create new environments in private and public clouds. wily juju 1.25.0 can maintain environments back to 1.18.1 (including 1.24.7 which wily currently has). Upgrades of clients and environments from juju 1.24.7 to 1.25.0 work without need of configuration changes. wily juju 1.25.0 can manually provision environments and add-machines. ** Tags removed: verification-needed ** Tags added: ification-done-wily ver verification-done-xenial ** Tags removed: ification-done-wily ver ** Tags added: verification-done-wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1510565 Title: [needs-packaging] Juju 1.25.0 is not in xenial and wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1510565/+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 1512185] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1512185 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] [NEW] qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Public bug reported:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for
amd64/x86_64.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep
[Bug 1506652] Re: [needs-packaging] Juju 1.24.7 is not in Ubuntu
I certify that juju 1.24.7 is suitable for local charm development and testing using both trusty and vivid containers. Users of vivid juju 1.24.7 can create new environments in private and public clouds. Vivid juju 1.24.7 can maintain environments back to 1.18.1 (including 1.24.6 which vivid currently has). Upgrades of clients and environments from juju 1.24.6 to 1.24.7 work without need of configuration changes. vivid juju 1.24.7 can manually provision environments and add-machines. ** Tags removed: verification-needed ** Tags added: verification-dont-vivid verification-needed-trusty ** Tags removed: verification-dont-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1506652 Title: [needs-packaging] Juju 1.24.7 is not in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1506652/+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 1506652] Re: [needs-packaging] Juju 1.24.7 is not in Ubuntu
I certify that juju 1.24.7 is suitable for local charm development and testing using both trusty and vivid containers. Users of vivid juju 1.24.7 can create new environments in private and public clouds. Vivid juju 1.24.7 can maintain environments back to 1.18.1 (including 1.24.6 which vivid currently has). Upgrades of clients and environments from juju 1.24.6 to 1.24.7 work without need of configuration changes. vivid juju 1.24.7 can manually provision environments and add-machines. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1506652 Title: [needs-packaging] Juju 1.24.7 is not in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1506652/+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
