[Bug 1159818] Re: Allow architecture armhf with template ubuntu-cloud when running on ARM
This was fixed by smoser and pushed to trunk. Here is a diff if you're interested: https://pastebin.canonical.com/99718/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1159818 Title: Allow architecture armhf with template ubuntu-cloud when running on ARM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1159818/+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 1287265] [NEW] Fixes required to run on trusty
Public bug reported: I had to do some source code changes to be able to run Horizon on trusty. Here is a list of change in a form of error message followed by solution. Can we update the package to be able to run it just from the box? === File /usr/lib/python2.7/dist-packages/openstack_auth/urls.py, line 14, in module from django.conf.urls.defaults import patterns, url ImportError: No module named defaults === /usr/share/pyshared/openstack_auth/urls.py: - from django.conf.urls.defaults import patterns, url + from django.conf.urls import patterns, url === File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/__init__.py, line 36, in module from openstack_dashboard.api import base ImportError: cannot import name base === /usr/share/openstack-dashboard/openstack_dashboard/api/__init__.py - from openstack_dashboard.api import base - from openstack_dashboard.api import ceilometer - from openstack_dashboard.api import cinder - from openstack_dashboard.api import fwaas - from openstack_dashboard.api import glance - from openstack_dashboard.api import heat - from openstack_dashboard.api import keystone - from openstack_dashboard.api import lbaas - from openstack_dashboard.api import network - from openstack_dashboard.api import neutron - from openstack_dashboard.api import nova - from openstack_dashboard.api import swift - from openstack_dashboard.api import trove - from openstack_dashboard.api import vpn + import base + import ceilometer + import cinder + import fwaas + import glance + import heat + import keystone + import lbaas + import network + import neutron + import nova + import swift + import trove + import vpn = File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/trove.py, line 20, in module from troveclient.v1 import client ImportError: No module named v1 = /usr/share/openstack-dashboard/openstack_dashboard/api/trove.py - from troveclient.v1 import client + from troveclient import client = File /usr/lib/python2.7/dist-packages/django/contrib/auth/forms.py, line 175, in __init__ super(AuthenticationForm, self).__init__(*args, **kwargs) TypeError: __init__() got multiple values for keyword argument 'data' = /usr/lib/python2.7/dist-packages/openstack_auth/forms.py:54 -super(Login, self).__init__(*args, **kwargs) +super(Login, self).__init__(**kwargs) ** Affects: horizon (Ubuntu) Importance: Undecided Status: New ** Description changed: I had to do some source code changes to be able to run Horizon on trusty. Here is a list of change in a form of error message followed by solution. Can we update the package to be able to run it just from the box? - + === - [Mon Mar 03 14:05:11.309641 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] Traceback (most recent call last): - [Mon Mar 03 14:05:11.309705 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] File /usr/lib/python2.7/dist-packages/django/core/handlers/wsgi.py, line 187, in __call__ - [Mon Mar 03 14:05:11.309970 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] self.load_middleware() - [Mon Mar 03 14:05:11.310010 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] File /usr/lib/python2.7/dist-packages/django/core/handlers/base.py, line 49, in load_middleware - [Mon Mar 03 14:05:11.310344 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] mw_instance = mw_class() - [Mon Mar 03 14:05:11.310384 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] File /usr/lib/python2.7/dist-packages/django/middleware/locale.py, line 24, in __init__ - [Mon Mar 03 14:05:11.310579 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] for url_pattern in get_resolver(None).url_patterns: - [Mon Mar 03 14:05:11.310633 2014] [:error] [pid 2765:tid 3010790448] [remote 10.229.37.209:30131] File /usr/lib/python2.7/dist-packages/django/core/urlresolvers.py, line 346, in url_patterns - [Mon Mar 03
[Bug 1301516] [NEW] apparmor prevents libvirt from running qemu-system-aarch64
Public bug reported: While trying to run openstack-nova/libvirt on arm64 machine we got the following error: libvirtd.log 2014-04-02 16:08:11.140+: 1227: error : qemuProcessWaitForMonitor:1915 : internal error: process exited while connecting to monitor: libvirt: error : cannot execute binary /usr/bin/qemu-system-aarch64: Permission denied /var/log/kern.log Apr 2 12:34:57 ms01a kernel: [ 2133.890335] type=1400 audit(1396456497.933:59): apparmor=DENIED operation=exec profile=libvirt-be2523fd-4c0a-43f0-afa9-c46122f2cf81 name=/usr/bin/qemu-system-aarch64 pid=6241 comm=libvirtd requested_mask=x denied_mask=x fsuid=111 ouid=0 AppArmor prevents libvirtd from running qemu-system-aarch64 because this binary name is not listed in: /etc/apparmor.d/abstractions/libvirt-qemu ... # the various binaries /usr/bin/kvm rmix, /usr/bin/qemu rmix, /usr/bin/qemu-system-arm rmix, /usr/bin/qemu-system-cris rmix, /usr/bin/qemu-system-i386 rmix, ... The following patch fixes the issue: --- libvirt-1.2.2-0/debian/apparmor/libvirt-qemu2014-04-02 12:51:03.013539000 -0400 +++ libvirt-1.2.2/debian/apparmor/libvirt-qemu 2014-04-02 12:54:18.653539000 -0400 @@ -83,6 +83,7 @@ /usr/bin/kvm rmix, /usr/bin/qemu rmix, /usr/bin/qemu-system-arm rmix, + /usr/bin/qemu-system-aarch64 rmix, /usr/bin/qemu-system-cris rmix, /usr/bin/qemu-system-i386 rmix, /usr/bin/qemu-system-m68k rmix, ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: hs-arm64 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1301516 Title: apparmor prevents libvirt from running qemu-system-aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1301516/+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 1316579] [NEW] --upload-tools doesn't work with bootstrap on armhf machine managed by maas
Public bug reported:
ubuntu@mw01-02:~$ juju --version
1.18.1-trusty-armhf
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
ubuntu@mw01-02:~/juju$ juju bootstrap --constraints arch=armhf --upload-tools
--debug
2014-05-06 11:07:49 DEBUG juju.environs.simplestreams simplestreams.go:985
metadata: {map[com.ubuntu.cloud:server:12.04:amd64:{precise 12.04 amd64
map[20140408:0x114c2390 20140227:0x114c2780]}
com.ubuntu.cloud:server:13.10:amd64:{saucy 13.10 amd64
map[20140227:0x114c2ab0 20140410:0x114c2cf0]}
com.ubuntu.cloud:server:14.04:amd64:{trusty 14.04 amd64
map[20140416:0x114c2f60]}] map[crsn:map[euww1:map[region:eu-ams-1
endpoint:https://eu-ams-1.api.joyentcloud.com] ussw1:map[region:us-sw-1
endpoint:https://us-sw-1.api.joyentcloud.com] usww1:map[region:us-west-1
endpoint:https://us-west-1.api.joyentcloud.com] usee1:map[region:us-east-1
endpoint:https://us-east-1.api.joyentcloud.com]]] Thu, 17 Apr 2014 18:22:18
+ products:1.0 com.ubuntu.cloud:released:joyent}
2014-05-06 11:07:49 ERROR juju.cmd supercommand.go:300 environment maas of
type maas does not support instances running on armhf
I can successfully use juju with this maas/armhf installation if I don't pass
'--upload-tools' flag to bootstrap.
What I'm doing wrong?
Thanks
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ ubuntu@mw01-02:~$ uname -a
+ Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
+
+ ubuntu@mw01-02:~$ cat /etc/lsb-release
+ DISTRIB_ID=Ubuntu
+ DISTRIB_RELEASE=14.04
+ DISTRIB_CODENAME=trusty
+ DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
+
ubuntu@mw01-02:~/juju$ juju bootstrap --constraints arch=armhf --upload-tools
--debug
2014-05-06 11:07:49 DEBUG juju.environs.simplestreams simplestreams.go:985
metadata: {map[com.ubuntu.cloud:server:12.04:amd64:{precise 12.04 amd64
map[20140408:0x114c2390 20140227:0x114c2780]}
com.ubuntu.cloud:server:13.10:amd64:{saucy 13.10 amd64
map[20140227:0x114c2ab0 20140410:0x114c2cf0]}
com.ubuntu.cloud:server:14.04:amd64:{trusty 14.04 amd64
map[20140416:0x114c2f60]}] map[crsn:map[euww1:map[region:eu-ams-1
endpoint:https://eu-ams-1.api.joyentcloud.com] ussw1:map[region:us-sw-1
endpoint:https://us-sw-1.api.joyentcloud.com] usww1:map[region:us-west-1
endpoint:https://us-west-1.api.joyentcloud.com] usee1:map[region:us-east-1
endpoint:https://us-east-1.api.joyentcloud.com]]] Thu, 17 Apr 2014 18:22:18
+ products:1.0 com.ubuntu.cloud:released:joyent}
2014-05-06 11:07:49 ERROR juju.cmd supercommand.go:300 environment maas of
type maas does not support instances running on armhf
I can successfully use juju with this maas/armhf installation if I don't pass
'--upload-tools' flag to bootstrap.
What I'm doing wrong?
Thanks
--
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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
maas
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1316579/+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 1316582] [NEW] juju command spontaneously hangs/crashes while running on armhf
Public bug reported:
ubuntu@mw01-02:~$ juju --version
1.18.1-trusty-armhf
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
ubuntu@mw01-02:~$ juju bootstrap --constraints arch=armhf --debug
...
Running apt-get update
Installing package: git
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: juju-mongodb
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed
%{speed_download} bytes/s ' -o $bin/tools.tar.gz
'https://streams.canonical.com/juju/tools/releases/juju-1.18.2-trusty-armhf.tgz'
Starting MongoDB server (juju-db)
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
2014-05-06 11:15:50 INFO juju.cmd supercommand.go:306 command finished
HANGS
ubuntu@mw01-02:~$ juju status
environment: maas
machines:
0:
agent-state: started
agent-version: 1.18.2
dns-name: mw01-04.1ss
instance-id: /MAAS/api/1.0/nodes/node-8cd85c4e-d062-11e3-bdfd-000173020cf5/
series: trusty
services:
mysql:
charm: local:trusty/mysql-311
exposed: false
relations:
cluster:
- mysql
units:
mysql/0:
agent-state: started
agent-version: 1.18.2
machine: 0
public-address: mw01-04.1ss
wordpress:
charm: local:trusty/wordpress-93
exposed: false
relations:
loadbalancer:
- wordpress
units:
wordpress/0:
agent-state: pending
agent-version: 1.18.2
machine: 0
public-address: mw01-04.1ss
HANGS
When application hangs I observe the following issue in ps:
ubuntu@mw01-02:~$ ps aux | grep juju
ubuntu9696 47.7 0.0 0 0 pts/0Zl+ 12:11 3:38 [juju]
defunct
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
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/1316582
Title:
juju command spontaneously hangs/crashes while running on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1316582/+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 1316579] Re: --upload-tools doesn't work with bootstrap on armhf machine managed by maas
** Description changed:
+ ubuntu@mw01-02:~$ juju --version
+ 1.18.1-trusty-armhf
+
ubuntu@mw01-02:~$ uname -a
Linux mw01-02 3.13.0-24-generic-lpae #46-Ubuntu SMP Thu Apr 10 21:01:14 UTC
2014 armv7l armv7l armv7l GNU/Linux
- ubuntu@mw01-02:~$ cat /etc/lsb-release
+ ubuntu@mw01-02:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
ubuntu@mw01-02:~/juju$ juju bootstrap --constraints arch=armhf --upload-tools
--debug
2014-05-06 11:07:49 DEBUG juju.environs.simplestreams simplestreams.go:985
metadata: {map[com.ubuntu.cloud:server:12.04:amd64:{precise 12.04 amd64
map[20140408:0x114c2390 20140227:0x114c2780]}
com.ubuntu.cloud:server:13.10:amd64:{saucy 13.10 amd64
map[20140227:0x114c2ab0 20140410:0x114c2cf0]}
com.ubuntu.cloud:server:14.04:amd64:{trusty 14.04 amd64
map[20140416:0x114c2f60]}] map[crsn:map[euww1:map[region:eu-ams-1
endpoint:https://eu-ams-1.api.joyentcloud.com] ussw1:map[region:us-sw-1
endpoint:https://us-sw-1.api.joyentcloud.com] usww1:map[region:us-west-1
endpoint:https://us-west-1.api.joyentcloud.com] usee1:map[region:us-east-1
endpoint:https://us-east-1.api.joyentcloud.com]]] Thu, 17 Apr 2014 18:22:18
+ products:1.0 com.ubuntu.cloud:released:joyent}
2014-05-06 11:07:49 ERROR juju.cmd supercommand.go:300 environment maas of
type maas does not support instances running on armhf
I can successfully use juju with this maas/armhf installation if I don't pass
'--upload-tools' flag to bootstrap.
What I'm doing wrong?
Thanks
--
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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
maas
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1316579/+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 1432683] [NEW] apt-get install lxc doesn't load required apparmor profiles
Public bug reported: I'm trying to use LXC on my openstack instance which runs vivid daily: $ sudo apt-get install lxc -y $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache --stream=daily --release=vivid $ sudo lxc-start --name vivid --logfile=lxc.log lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. In the log file (lxc.log) I observe the following error: lxc-start 1426516387.814 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - failed to change apparmor profile to lxc-container-default This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not loaded appropriately. This issue disappears if I: (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload or (b) reboot the instance I'd expect that 'apt-get install lxc' has to load all appropriate apparmor profiles to allow starting containers w/o profile reloading / rebooting. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm trying to use LXC on my openstack instance which runs vivid daily: $ sudo apt-get install lxc -y $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache --stream=daily --release=vivid $ sudo lxc-start --name vivid --logfile=lxc.log lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. In the log file (lxc.log) I observe the following error: lxc-start 1426516387.814 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - failed to change apparmor profile to lxc-container-default This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not loaded appropriately. This issue disappears if I: (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload or (b) reboot the instance - I'd expert that 'apt-get install lxc' has to load all appropriate + I'd expect that 'apt-get install lxc' has to load all appropriate apparmor profiles to allow starting containers w/o profile reloading / rebooting. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1432683 Title: apt-get install lxc doesn't load required apparmor profiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1432683/+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 1432683] Re: apt-get install lxc doesn't load required apparmor profiles
Hi Serge, Many thanks for looking at the bug. Here is information you requested. ubuntu@vivid-lxc-bug:~$ uname -a Linux vivid-lxc-bug 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ubuntu@vivid-lxc-bug:~$ sudo aa-status apparmor module is loaded. 6 profiles are loaded. 6 profiles are in enforce mode. /sbin/dhclient /usr/bin/lxc-start /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/sbin/tcpdump 0 profiles are in complain mode. 1 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /sbin/dhclient (508) /tmp/debug.out: http://paste.ubuntu.com/10614837/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1432683 Title: apt-get install lxc doesn't load required apparmor profiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1432683/+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 1432715] Re: tomcat7 ftbfs in vivd (test failures)
It seems that this bug consists of many partially independent bugs. I found at least two: (1) openjdk in vivid has SSLv3 disable but tests try to use it and get 'protocol is disabled or cipher suites are inappropriate' as a warkaround you may enable sslv3 back by commenting the following line in /etc/java-7-openjdk/security/java.security: # jdk.tls.disabledAlgorithms=SSLv3 (2) another issue is that certificates inside the package expired which leads to SSL errors here and there for example: $ head test/org/apache/tomcat/util/net/localhost-cert.pem Certificate: Data: Version: 3 (0x2) Serial Number: 4099 (0x1003) Signature Algorithm: sha1WithRSAEncryption Issuer: C=US, CN=ca-test.tomcat.apache.org Validity Not Before: Feb 28 05:28:42 2013 GMT Not After : Feb 28 05:28:42 2015 GMT Subject: C=US, CN=localhost Note Feb 28 2015 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1432715 Title: tomcat7 ftbfs in vivd (test failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1432715/+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 1432715] Re: tomcat7 ftbfs in vivd (test failures)
They have updated certs in trunk: http://mail-archives.apache.org/mod_mbox/tomcat-dev/201502.mbox/%3c20150228182330.eaaabac0...@hades.apache.org%3E We may just pick them up. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1432715 Title: tomcat7 ftbfs in vivd (test failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1432715/+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 1432715] Re: tomcat7 ftbfs in vivd (test failures)
Some part of bugs disappear when I put updated certs (with expiration date in
2017) from here:
https://github.com/apache/tomcat/test/org/apache/tomcat/util/net/{localhost-cert.pem,
localhost-copy1.jks, localhost.jks, localhost-key.pem}
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1432715
Title:
tomcat7 ftbfs in vivd (test failures)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1432715/+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 1432715] Re: tomcat7 ftbfs in vivd (test failures)
** Changed in: tomcat7 (Ubuntu Vivid) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1432715 Title: tomcat7 ftbfs in vivd (test failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1432715/+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 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
Shell script which reproduces the issue: http://pastebin.ubuntu.com/10712595/ Please run this script only on a disposable instance in the cloud because it creates and adds ultimately trusted certificate to the target machine. I was able to reproduce the issue on precise (12.04) and trusty (14.04). I *was not* able to reproduce the issue on utopic (14.10) and vivid (15.04). This happens because libldap is linked against later version of libgnutls in 14.10 and 15.04. 12.04 and 14.04 use 2.x generation of libgnutls while 14.10 and 15.04 use 3.x generation. I assume that libgnutls 3.x does proper cleanup and doesn't return semi-initialized context on errors (which was the root cause of the bug). Please note that this issue doesn't crash ldap server itself but only clients who passes incorrect SSL/TLS-related settings into libldap using ldap_set_option(NULL, LDAP_OPT_X_TLS_CIPHER_SUITE, NAME). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+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 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
** Changed in: openldap (Ubuntu Precise) Status: New = In Progress ** Changed in: openldap (Ubuntu Trusty) Status: New = In Progress ** Changed in: openldap (Ubuntu Precise) Assignee: (unassigned) = Oleg Strikov (strikov) ** Changed in: openldap (Ubuntu Trusty) Assignee: (unassigned) = Oleg Strikov (strikov) ** Changed in: openldap (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+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 1438788] Re: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Hi Argenis, Thanks for reporting the bug. I was not able to reproduce the bug on a fresh installation of 15.04. It looks like this issue happens when you upgrade the package from ubuntu4 to ubuntu5. I think that the following workaround may resolve the issue: $ sudo rm /etc/systemd/system/mysql.service After running this command you (theoretically) should be able to purge and install the package w/o any issue. Please let us now if it helps you or not. ** Changed in: mysql-5.6 (Ubuntu) Assignee: (unassigned) = Oleg Strikov (strikov) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1438788 Title: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1438788/+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 1416039] Re: Broken apparmor profile
Hi Jacek, Thanks for reporting the bug and providing us with the fix. I prepared a debdiff (attached) and will be looking for sponsorship. ** Patch added: lp-1416039.debdiff https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416039/+attachment/4333549/+files/lp-1416039.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1416039 Title: Broken apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416039/+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 1416039] Re: Broken apparmor profile
** Changed in: squid3 (Ubuntu) Assignee: (unassigned) = Oleg Strikov (strikov) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1416039 Title: Broken apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416039/+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 1424508] Re: upstartism in the maintainer script
Thanks for pointing that. Done. ** Patch added: lp-1424508-proposed-1.debdiff https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335313/+files/lp-1424508-proposed-1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1424508 Title: upstartism in the maintainer script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+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 1336742] Re: Caching responses with Vary header
I prepared a debdiff for vivid (attached) and currently looking for sponsorship. My repro case can be found here: http://pastebin.ubuntu.com/10527246/ ** Patch added: lp-1336742-vivid.debdiff https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1336742/+attachment/4334428/+files/lp-1336742-vivid.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1336742/+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 1424508] Re: upstartism in the maintainer script
I prepared debdiff for vivid-release (attached) and currently looking for sponsorship. ** Patch added: lp-1424508-released.debdiff https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335137/+files/lp-1424508-released.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1424508 Title: upstartism in the maintainer script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+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 1424508] Re: upstartism in the maintainer script
I prepared debdiff for vivid-proposed (attached) and currently looking for sponsorship. ** Patch added: lp-1424508-proposed.debdiff https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+attachment/4335136/+files/lp-1424508-proposed.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1424508 Title: upstartism in the maintainer script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+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 1336742] Re: Caching responses with Vary header
Updated package has been pushed to vivid-proposed. Feel free to try it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1336742/+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 1424508] Re: upstartism in the maintainer script
My reprocase can be found here: http://paste.ubuntu.com/10538557/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1424508 Title: upstartism in the maintainer script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1424508/+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 1447200] [NEW] juju-core 1.23.1 is not packaged in Ubuntu
Public bug reported: We're now in a position to have 1.23.1 enter trusty-proposed and vivid- proposed, but it should not land in trusty or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Development Fix] Upload of new upstream release with packaging review. [strikov] will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid. [Stable Fix] Full backport of new upstream release. [Pre-QA tasks] [strikov] Upload to the development release (vivid-proposed): TODO [strikov] Upload to the current LTS release (trusty-proposed): TODO [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upsteam QA test against Vivid: TODO [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [sinzui] Test juju-quickstart against vivid-proposed: TODO [sinzui] Test juju-quickstart against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed -- 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/1447200 Title: juju-core 1.23.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1447200/+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 1438745] Re: package clamav-daemon 0.98.6+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Verification done. Logs: http://pastebin.ubuntu.com/10880409/ ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1438745 Title: package clamav-daemon 0.98.6+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1438745/+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 1438745] Re: package clamav-daemon 0.98.6+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Debdiff attached. [SRU] [Impact] Bug shows up when user tries to upgrade any previous version of clamav to the version which is currently available inside vivid repo. Apt crashes with the following error message: /var/lib/dpkg/info/clamav-daemon.postinst: 626: /var/lib/dpkg/info/clamav-daemon.postinst: cannot create : Directory nonexistent dpkg: error processing package clamav-daemon (--install): subprocess installed post-installation script returned error exit status 2 This happens due to a typo inside postinst script. Variable $DEBCONFILE is used incorrectly instead of $DEBCONFFILE (note double F) which leads to generation of the incorrect output path. This typo is on the path which gets executed only when debconf information is available for the package. It means that the issue doesn't show up during regular installation but crashes apt during updates. This issue is important because all clamav users will observe the issue while upgrading from Utopic to Vivid. [Test Case] How to reproduce the issue and make sure that debdiff resolves it: http://pastebin.ubuntu.com/10879650/ [Regression Potential] Change is minor and fixes obvious issue. We can't avoid fixing it because with this issue in place we won't be able to upgrade clamav in the future (all vivid users will meet this issue if we upload an updated package without this change). ** Patch added: clamav-sru-1438745.debdiff https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1438745/+attachment/4383128/+files/clamav-sru-1438745.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1438745 Title: package clamav-daemon 0.98.6+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1438745/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
Thanks Curtis! Adding 'verification-done' tag based on your comments. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
There was a typo in the message #8 from Curtis. Juju 1.22.1 has been certified not 1.20.1. sinzui strikov, oops, yes, I do mean *1.22.1* -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
Hi Curtis, To my understanding juju-1.22.1 is not in -updates yet not because we don't want this but because it needs to be in -proposed for 7 days before reaching -updates. This is a standard practice for SRUs. I expect to see it landed into -updates until the end of this week. If juju team wants to have it landed *right now* -- please let us now and we'll discuss it with the SRU team. Taking into account that 1.22.4 we'll be in -proposed for 7 days as well, I think that we may want to land 1.22.1 first. What is your opinion? -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1443542] Re: curtin race on vivid when /dev/sda1 doesn't exist
Execution of blockdev --rereadpt simply issues a call to ioctl(BLKRRPART) which forces kernel to re-initialize its metadata. Kernel adds information about newly created partition here: http://lxr.linux.no/#linux+v3.19.1/block/partition-generic.c#L269 You can see a call to kobject_uevent() which puts event to udev's queue. So to me it looks like udev settle should have all the information available. Only if blockdev succeeds though. We don't check its return code if I got it correctly. Another interesting point is that there are two popular ways to re-read the partition table: BLKRRPAR ioctl (used by blockdev) and BLKPG ioctl (used by partprobe). They are very different. While BLKRRPAR lets kernel know that partition table needs to be re-read, BLKPG tells kernel the exact partitioning layout (parted does this because it wants to have ultimate control over things). BLKPG may be more udev-friendly because parted-based tools are more popular. We may want to try partprobe instead of blockdev and see if it solves the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1443542 Title: curtin race on vivid when /dev/sda1 doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1443542/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
Adding verification-failed based on #14 ** Tags removed: verification-done ** Tags added: verification-failed -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
** Project changed: juju-core = juju-core (Ubuntu) -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
** Changed in: juju-core (Ubuntu) Assignee: Curtis Hovey (sinzui) = (unassigned) ** Changed in: juju-core (Ubuntu) Assignee: (unassigned) = Oleg Strikov (strikov) ** Changed in: juju-core (Ubuntu Trusty) Assignee: (unassigned) = Oleg Strikov (strikov) -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
Removing 'block-proposed' flag to allow juju 1.22.1 to go into Vivid. ** Description changed: We're now in a position to have 1.22.1 enter trusty-proposed and vivid- proposed, but it should not land in trusty or vivid until upstream passes QA on our proposed binaries, published the tools in their stable simplestream and announces the release for general production use. [SRU Information] juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates. [Development Fix] Upload of new upstream release with packaging review. [strikov] will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid. [Stable Fix] Full backport of new upstream release. [Pre-QA tasks] - [strikov] Upload to the development release (vivid-proposed): TODO + [strikov] Upload to the development release (vivid-proposed): DONE [strikov] Upload to the current LTS release (trusty-proposed): TODO [QA Status] Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block- proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately. [sinzui] Upsteam QA test against Vivid: DONE [sinzui] Upstream QA test against Trusty: TODO [sinzui] Upstream release process complete: TODO Manual tests required: [sinzui] Test juju-quickstart against vivid-proposed: DONE [sinzui] Test juju-quickstart against trusty-proposed: TODO The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug. Landscape team QA: TODO ** Tags removed: block-proposed -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
Here is the changelog for the package I'm asking SRU for: juju-core (1.22.1-0ubuntu0.14.04.1) trusty; urgency=medium * New upstream release (LP: #1444037). * Packaging changes required by the new release and cherry-picked from Vivid: - d/tests/fake-future.sh: New ability to generate fake /etc/os-release. Change is needed to provide Juju 1.22.1 with an appropriate testbed. - d/control: Juju-local now depends on cloud-image-utils | cloud-utils. Juju uses ubuntu-cloud template which in turn uses cloud-image-utils. Package lxc-templates only recommends cloud-image-utils hence Juju needs to require this package directly. Package cloud-utils is mentioned as an alternative because cloud-image-utils is not available on precise but we want to unify Juju packaging for all supported releases. - d/copyright: Updated to reflect changes in the codebase. * Compliance to Debian Policy 3.9.6 was declared. Few comments about the changes: (1) d/tests/fake-future.sh change is absolutely required by the new release. Without this change future-local-provider and future-manual- provider autopkgtests fail. These tests check if Juju can live inside new development release (when version and codename change) and proposed change extends emulation layer by generating fake /etc/os-release. Juju didn't process /etc/os-release before hence we need this change only for 1.22+. (2) d/control change has been cherry-picked from Vivid because (a) not fixing this bug will lead to issues with juju when lxc-templates package have been installed w/o recommends (b) we want to minimize packaging delta between supported releases. (3) d/copyright change is needed because code base changed and we have to react by providing up-to-date d/copyright. It also helps to minimize packaging delta. (4) Compliance to Debian Policy 3.9.6 has been declared to minimize packaging delta. I don't see any regression potential here. We still have some delta between 1.22.1 in Vivid and Trusty: (1) Version in Trusty has explicit build dependency on libgo5 (= 4.9.1-0ubuntu1) [!amd64 !i386 !armhf] This change addressed the following issue: https://bugs.launchpad.net/juju-core/+bug/1377325 While 4.9.1-0ubuntu1 is the current version of the package in Trusty I don't see any reason to remove this explicit versioned dependency. It minimizes SRU delta and potential regression risk. (2) Version in Vivid have autopkgtests modified to revert back to upstart before running tests. This is needed because Juju 1.22.* doesn't support systemd which is default init system in Vivid. This delta will be removed with Juju 1.23 release which supports systemd. -- 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/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1416051] Re: juju-core 1.22.0 is not packaged in Ubuntu
Tag block-proposed has been removed to be able to update the package in vivid. We don't plan to update trusty package with 1.22.0 for now. I'll post an update to this bug when we make decision on package update in trusty. ** Tags removed: block-proposed -- 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/1416051 Title: juju-core 1.22.0 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1416051/+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 1416051] Re: juju-core 1.22.0 is not packaged in Ubuntu
Juju 1.22.0 can't provision instances which run vivid because it doesn't support systemd. Systemd support has been introduced in Juju 1.23 and we plan to package this release when it becomes stable (now in beta). However, I think that having 1.22 in vivid is much better than having Juju 1.20 (what we currently have) taking into account that 1.20 doesn't support vivid as well. We get new features of Juju 1.22 and can use them against trusty and precise instances. Due to the fact that Juju 1.22 can't provision instances which run vivid, many dep8 autotests fail. These tests rely on juju local provider (LXC) and expect to have upstart running on both host machine and guest instance. I made decision to avoid modifying tests because this operation is needed only for 1.22 and will be reverted while packaging 1.23. To do functional testing I modified the image adt-run uses and manually installed upstart there. Then, I run adt-run and get all tests passed: http://paste.ubuntu.com/10760926/ I think that this can be counted as equivalent to the regular autotests run which is carried out automatically against package in -proposed. Curtis Hovey (sinzui) from Juju Team carried out all the testing procedures required (see #2) and we are ready to move juju-1.22.0 package from -proposed to release. This can't be done automatically (dep8 tests fail) that's why I'm asking for sponsorship to *manually* move the package to release repo. -- 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/1416051 Title: juju-core 1.22.0 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1416051/+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 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
I plan to change the status of this bug for 12.04 (precise) and 14.04 (trusty) to Won't Fix. In this comment I want to explain why I came to this decision. This bug had CVE-2013-4449 linked to it. I don't think that this CVE is relevant because the patch proposed in this bug doesn't resolve the issue mentioned in the description of this CVE. I proved that by using the following repro script: http://pastebin.ubuntu.com/10764620/ This script is derived from the repro case provided in the debian bug for CVE-2013-4449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729367#22 [!] Please note that this CVE can be reliably reproduced only on multicore machine (e.g. you can't use m1.small cloud instance). Some form of race condition takes place and your chances are much higher on multicore. When CVE-2013-4449 is resolved this script should print 'Finished' at the end of execution. When CVE is still here it prints 'No server found on localhost:389 attempt'. 'No server found' means that slapd crashed and can't be accessed via network and 'attempt' is a number of iteration when slapd crashed (it usually takes from 3 to 15 iterations because some form of race condition needs to take place). WITH and WITHOUT the proposed patch I get 'No server found' message on 12.04 (precise) and 14.04 (trusty). It means that patch doesn't fix CVE-2013-4449. Patch doesn't fix CVE-2013-4449 but it still can fix the issue mentioned in the bug description (incorrect cipher suite string leads to a crash). That's true but I don't think that we want to update 12.04 (precise) and 14.04 (trusty). ANY update may lead to unpredictable regressions (see https://wiki.ubuntu.com/StableReleaseUpdates) and the profit of patching should exceed the amount of potential issues it may create. OpenLDAP is an important infrastructural component and we need to have a very good reason to update it. I don't see such a reason. Client may crash itself by passing incorrect cipher suite to the API. While that's sad, it doesn't crash slapd itself and doesn't create any inconveniences to other users. This looks like a good fix for a development release but not stable release. Please let me know if you have any objections or additional information about this bug. We're open to discussion and can re-open this bug if needed. Thanks to Jouko Orava and others for opening this bug and taking part in the discussion. ** Bug watch added: Debian Bug tracker #729367 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729367 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-4449 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+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 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash
Hi Harry, Thanks for the input. Could you add more information on this please: silently switch from a slapd that used openssl to gnutls I just looked through the launchpad package archive and it looks like we never had openldap linked against openssl in 12.04 and 14.04. First version of openldap which showed up in 12.04 was 2.4.25 and it has libgnutls-dev in build dependencies. Do you mean upgrading from any previous release to precise/trusty? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1103353 Title: Invalid GnuTLS cipher suite strings causes libldap to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+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 1438788] Re: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
I plan to change the status of this bug to Won't Fix and here is the explanation for this decision. We can theoretically fix this issue in mysql package. In the postrm handler we need to check if this problematic symlink exists and remove it before passing control to deb- systemd-helper. I don't think this is reasonable decision though. If we put this code into the package we'd be required to leave it there forever (users may upgrade from buggy ubuntu4 to ubuntu5-6-7-8 and then make decision to remove the package). Keeping it there forever is bad because we're doing systemd's and deb-systemd-helper's work by managing symlinks inside /etc/systemd/system/ and this fact may lead to unpredictable issues in the future. Workaround (see above) is pretty straightforward and shouldn't create any issues for vivid users. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1438788 Title: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1438788/+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 1439793] [NEW] deb-systemd-helper crashes while removing packages with unusual (but legal) Alias in unit config
Public bug reported:
While working on mysql-5.6 package we met unusual (maybe even partially
incorrect) Alias option in systemd unit config:
Alias=mysql.service
It is unusual because mysql.service is the original name of the service which
can be found inside /lib/systemd/system/... This Alias option doesn't make
any sense (mysql service will be accessible as mysql.service even without this
alias) and my assumption is that it was created because the author was not sure
if it's okay not to have any aliases at all or you need at least one. Anyhow
this seems to be legal to do that (i was not able to find any documents which
state that this is incorrect) even if it's something useless.
Installation went well and the following alias symlink has been created:
/etc/systemd/system/mysq.service -- /lib/systemd/system/mysql.service
Service was accessible via systemctl and everything was fine.
When you try to remove/purge the package you get the following error:
/usr/bin/deb-systemd-helper: error: unable to link
/etc/systemd/system/mysql.service to /dev/null: File exists
This happens because deb-systemd-helper tries to 'mask' service the following
way:
sub mask_service {
my ($scriptname, $service_path) = @_;
my $mask_link = '/etc/systemd/system/' . basename($service_path);
if (-e $mask_link) {
# If the link already exists, don’t do anything.
return if -l $mask_link readlink($mask_link) eq '/dev/null';
debug $mask_link already exists, not masking.;
return;
}
make_path(dirname($mask_link));
symlink('/dev/null', $mask_link) or
error(unable to link $mask_link to /dev/null: $!);
...
}
Check for '-e $mask_link' FAILS because symlink's TARGET
(/lib/systemd/system/mysql.service) doesn't exists while doing postrm
and '-e' FOLLOWS symlinks. That's why we go to symlink(...) call
directly which fails because symlink already exists.
WORKAROUND: If apt-get remove/purge crashes with the error mentioned
above you need to manually remove symlink inside /etc/systemd/system
(/etc/systemd/system/mysql.service in our case) and rerun apt-get
remove/purge.
I'm not sure if we want to fix that.
On one hand, this situation is pretty rare.
On other hand though, such Alias=original-name situation is somewhat legal
and we may want to handle it correctly.
This issue with Alias= has been fixed (by removing this useless Alias)
in mysql-5.6 so that's not a blocker for us.
** Affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
While working on mysql-5.6 package we met unusual (maybe even partially
incorrect) Alias option in systemd unit config:
Alias=mysql.service
It is unusual because mysql.service is the original name of the service which
can be found inside /lib/systemd/system/... This Alias option doesn't make
any sense (mysql service will be accessible as mysql.service even without this
alias) and my assumption is that it was created because the author was not sure
if it's okay not to have any aliases at all or you need at least one. Anyhow
this seems to be legal to do that (i was not able to find any documents which
state that this is incorrect) even if it's something useless.
Installation went well and the following alias symlink has been created:
/etc/systemd/system/mysq.service -- /lib/systemd/system/mysql.service
Service was accessible via systemctl and everything was fine.
When you try to remove/purge the package you get the following error:
/usr/bin/deb-systemd-helper: error: unable to link
/etc/systemd/system/mysql.service to /dev/null: File exists
This happens because deb-systemd-helper tries to 'mask' service the following
way:
sub mask_service {
- my ($scriptname, $service_path) = @_;
+ my ($scriptname, $service_path) = @_;
- my $mask_link = '/etc/systemd/system/' . basename($service_path);
+ my $mask_link = '/etc/systemd/system/' . basename($service_path);
- if (-e $mask_link) {
- # If the link already exists, don’t do anything.
- return if -l $mask_link readlink($mask_link) eq '/dev/null';
+ if (-e $mask_link) {
+ # If the link already exists, don’t do anything.
+ return if -l $mask_link readlink($mask_link) eq '/dev/null';
- # If the file already exists, the user most likely copied the .service
- # file to /etc/ to change it in some way. In this case we don’t need
to
- # mask the .service in the first place, since it will not be removed
by
- # dpkg.
- debug $mask_link already exists, not masking.;
- return;
- }
+ debug $mask_link already exists, not masking.;
+ return;
+ }
- make_path(dirname($mask_link));
- symlink('/dev/null', $mask_link) or
- error(unable to link $mask_link to /dev/null: $!);
+ make_path(dirname($mask_link));
+ symlink('/dev/null', $mask_link) or
+
[Bug 1438788] Re: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
'I was able to reproduce the issue with upgrading the package (second part of the bug):' should be 'I was able to reproduce the issue with REMOVING the package (second part of the bug):' -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1438788 Title: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1438788/+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 1438788] Re: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Hi Argenis, Today I tried to upgrade from 5.6.23-1~exp1~ubuntu4 to 5.6.23-1~exp1~ubuntu5 and reproduce the issue you observed. Here is what I found: Upgrade from ~ubuntu4 to ~ubuntu5 runs smoothly. Mysql service starts after upgrade and automatically starts after reboot. I can't reproduce the fact that service doesn't start automatically. I assume that you observed the issue with autostart while using previous version of the package (~ubuntu4) i.e. one you used before the upgrade. Could you please confirm that? If so -- you met this bug: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1435823 It was fixed in the latest version of the package. I was able to reproduce the issue with upgrading the package (second part of the bug): Removing mysql-server-5.6 (5.6.23-1~exp1~ubuntu5) ... /usr/bin/deb-systemd-helper: error: unable to link /etc/systemd/system/mysql.service to /dev/null: File exists Please note that this issue is not related to the latest package (~ubuntu5) itself. It happens because the previous version (~ubuntu4) created incorrect symlink at /etc/systemd/system/ which can't be removed while removing the package. Latest version of the package won't create this symlink but you need to manually remove the link created by the previous version of the package. Once you do it -- you won't observe this issue in future. To fix this issue run the following command when apt-get remove/purge crashes: $ sudo rm /etc/systemd/system/mysql.service Now, re-run remove/purge. It should finish correctly this time. After carrying out this procedure you can reinstall mysql back. You won't observe the issue again. You may use this bug as a reference: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1436178 Please try to apply this workaround and let us know if it helps you or not. Thanks for reporting the bug! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1438788 Title: package mysql-server-5.6 5.6.23-1~exp1~ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1438788/+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
