[Bug 1356012] Re: maas incorrectly overmanages DNS reverse zones

** Changed in: maas/trunk Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1356012 Title: maas incorrectly overmanages DNS reverse zones To

[Bug 1518016] Update Released

The verification of the Stable Release Update for python- oslo.concurrency has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event

[Bug 1498370] Update Released

The verification of the Stable Release Update for neutron has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1499510] Update Released

The verification of the Stable Release Update for python-novaclient has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1518016] Re: [SRU] Nova kilo requires concurrency 1.8.2 or better

This bug was fixed in the package nova - 1:2015.1.2-0ubuntu2 --- nova (1:2015.1.2-0ubuntu2) vivid; urgency=medium * d/control: Bump oslo.concurrency to >= 1.8.2 (LP: #1518016). -- Corey Bryant Fri, 20 Nov 2015 07:56:47 -0500 ** Changed in: nova

[Bug 1499510] Re: [SRU] Fix Typo in socket attribute name in TCPKeepAliveAdapter

This bug was fixed in the package python-novaclient - 1:2.22.0-0ubuntu2 --- python-novaclient (1:2.22.0-0ubuntu2) vivid; urgency=medium * d/p/Fix-typo-in-socket-attribute-name.patch, d/p/Add-a-test-for-the-TCPKeepAliveAdapter.patch: Fix Typo in socket attribute name in

Re: [Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

On Nov 30, 2015, at 08:51 PM, Bryan Quigley wrote: >@barry.. Maybe do LiveCD tests on both of them to see if it's a >configuration issue or if it might be hardware related. I'd be very surprised if it was hardware, but I can try it. I never had this problem on this machine until this morning's

[Bug 1518016] Re: [SRU] Nova kilo requires concurrency 1.8.2 or better

This bug was fixed in the package python-oslo.concurrency - 1.8.2-0ubuntu0.15.04.1 --- python-oslo.concurrency (1.8.2-0ubuntu0.15.04.1) vivid; urgency=medium * New upstream point release, resolving incompatibilies in latest Nova stable kilo update with 1.8.0 (LP: #1518016).

[Bug 1498370] Re: [SRU] DHCP agent: interface unplug leads to exception

This bug was fixed in the package neutron - 1:2015.1.2-0ubuntu2 --- neutron (1:2015.1.2-0ubuntu2) vivid; urgency=medium * Fix DHCP agent delete non-existant interface (LP: #1498370) - d/p/dhcp-protect-against-case-when-device-name-is-none.patch -- Edward Hope-Morley

[Bug 1072221] Re: ELinks built without lua support

Debian reports this fixed in 0.12~pre6-9 and Ubuntu has had 0.12~pre6-10 since Wily, so I presume this is fixed in Ubuntu now also. Please explain and reopen if this is wrong. ** Changed in: elinks (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because

[Bug 1518016] Re: [SRU] Nova kilo requires concurrency 1.8.2 or better

** 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 nova in Ubuntu. https://bugs.launchpad.net/bugs/1518016 Title: [SRU] Nova kilo requires concurrency 1.8.2 or

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

Here is a non-OpenStack generic reproducer to re-confirm. Generic reproducer bundle: http://paste.ubuntu.com/13576737/ PASS: MAAS 1.9b2 + Juju 1.25.0 lxc units get unique IPs: http://paste.ubuntu.com/13576758/ FAIL: MAAS 1.9b2 + Juju 1.25.1 lxc units all have the same IP:

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

> I agree that we cannot move juju 1.25.1 out of proposed until the issue is > resolved. > Discussions between dimitern and mpontillo indicate that this is a maas > 1.9beta2+ > regression which changes in juju 1.25.1 exposed. It also exposed a bug in juju-core (it ignores the fact that the

[Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

This bug was fixed in the package lxc - 1.0.8-0ubuntu0.3 --- lxc (1.0.8-0ubuntu0.3) trusty; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) lxc (1.0.8-0ubuntu0.2) trusty; urgency=medium * Cherry-pick from upstream:

[Bug 1466458] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1497420] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1504496] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1515463] Re: Broken juju LXC deployments

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1441068] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1436723] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1516989] Re: juju status broken

fwereade is working on a script to repair an environment after this is hit in an upgrade. -- 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/1516989 Title: juju status broken To

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Thank you bq. Hrm, it's error -12218 SSL_ERROR_ENCRYPTION_FAILURE "Bulk data encryption algorithm failed in selected cipher suite." ** Changed in: nss (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which

[Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1517107] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1510619] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1517107] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)

This bug was fixed in the package lxc - 1.0.8-0ubuntu0.3 --- lxc (1.0.8-0ubuntu0.3) trusty; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) lxc (1.0.8-0ubuntu0.2) trusty; urgency=medium * Cherry-pick from upstream:

[Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1466458] Re: template 'none' doesn't work with lxc-create

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1515463] Re: Broken juju LXC deployments

This bug was fixed in the package lxc - 1.0.8-0ubuntu0.3 --- lxc (1.0.8-0ubuntu0.3) trusty; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) lxc (1.0.8-0ubuntu0.2) trusty; urgency=medium * Cherry-pick from upstream:

[Bug 1515463] Re: Broken juju LXC deployments

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1503330] Re: New upstream bugfix release 1.1.4 (LXC MRE)

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1515463] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1516971] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1514623] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1517107] Re: $PATH is getting clobbered when starting a container with Upstart

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1517107] Re: $PATH is getting clobbered when starting a container with Upstart

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1429140] Re: lxc-net upstart script fails on nonexistent iptables rules

This bug was fixed in the package lxc - 1.0.8-0ubuntu0.3 --- lxc (1.0.8-0ubuntu0.3) trusty; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) lxc (1.0.8-0ubuntu0.2) trusty; urgency=medium * Cherry-pick from upstream:

[Bug 1466458] Re: template 'none' doesn't work with lxc-create

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1497420] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1466458] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1441068] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3 --- lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

I just tested with the latest image (via testdrive). All I'm doing is, adding universe, installing chromium. On open the second tab fails to load (guessing it's login to Google), trying google.com or blogger.com also fails. I can also reproduce in canonistack, Marc and Chad I added your ssh

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changes to claim_sticky_ip_address

** Summary changed: - juju 1.25.1: lxc units all have the same IP address + juju 1.25.1: lxc units all have the same IP address - changes to claim_sticky_ip_address ** Summary changed: - juju 1.25.1: lxc units all have the same IP address - changes to claim_sticky_ip_address + juju 1.25.1:

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

I agree that we cannot move juju 1.25.1 out of proposed until the issue is resolved. Discussions between dimitern and mpontillo indicate that this is a maas 1.9beta2+ regression which changes in juju 1.25.1 exposed. -- You received this bug notification because you are a member of Ubuntu Server

[Bug 1521234] [NEW] ftbfs in xenial

Public bug reported: ftbfs in xenial ** Affects: squid3 (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Tags: ftbfs s390x ** Changed in: squid3 (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Tags added: ftbfs s390x

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

** Description changed: - With the proposed Juju 1.25.1, lxc units all possess the same IP address: + With MAAS 1.9b2 + proposed Juju 1.25.1, lxc units all possess the same IP address: http://paste.ubuntu.com/13499208/. - With stable Juju 1.25.0, lxc units get unique IP addresses as

[Bug 1330504] Re: strongSwan 5.1.3

FTBFS on s390x, building 5.3.5-1 from debian cannot be tested yet, as missing new (universe) dependencies. ** Tags added: s390x -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu.

[Bug 1330504] Re: strongSwan 5.1.3

Cherry-picking patch from debian upload 5.1.2-3 fixing the build failure, thus removing s390x tag for now. ** Tags removed: s390x -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu.

[Bug 1521234] Re: ftbfs in xenial

cherry-pick patch from debian 5.1.2-3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1521234 Title: ftbfs in xenial To manage notifications about this bug go to:

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

Andres, the issue with b2 is "maas device claim-sticky-ip- address " (which juju 1.25.1 uses, after creating a device for the container with parent it's host node) fails to allocate an address for the device, despite having properly configured ranges and available IPs. -- You received this bug

[Bug 1521240] [NEW] strongswan ftbfs on s390x

Public bug reported: strongswan ftbfs on s390x ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs s390x ** Tags added: ftbfs s390x -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 1521240] Re: strongswan ftbfs on s390x

This bug was fixed in the package strongswan - 5.1.2-0ubuntu8 --- strongswan (5.1.2-0ubuntu8) xenial; urgency=medium * Import FTBFS for s390x from Debian 5.1.2-3 upload. (LP: #1521240) -- Dimitri John Ledkov Mon, 30 Nov 2015 15:46:06 + ** Changed in:

[Bug 1514558] Re: New upstream bugfix release 1.1.5 (LXC MRE)

** Changed in: lxc (Ubuntu Vivid) Status: In Progress => Fix Released ** Changed in: lxc (Ubuntu Wily) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu.

[Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Changed in: lxc (Ubuntu Wily) Status: Fix Committed => Fix Released -- 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/1504496 Title: package lxc 1.1.4-0ubuntu0.1 failed to

[Bug 1429140] Update Released

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

@andreserl b2 About to upgrade to latest RC in our lab. -- 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/1519527 Title: juju 1.25.1: lxc units all have the same IP address -

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

@andreserl RC2 Please disregard my mentions of B2. Indeed I am using RC2. ** Description changed: - With MAAS 1.9b2 + proposed Juju 1.25.1, lxc units all possess the same IP address: + With MAAS 1.9rc2 + proposed Juju 1.25.1, lxc units all possess the same IP address:

[Bug 1503034] Re: Autofs 5.1.1-1ubuntu2 crashes with segfault on startup

In order for this to be SRUed to Wily, it needs to be made compliant with https://wiki.ubuntu.com/StableReleaseUpdates (Please add a rational, test case, and regression potential to the description of this bug.) -- You received this bug notification because you are a member of Ubuntu Server

[Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3 --- lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium * Cherry-pick from upstream: - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971) - Fix process title rewrite to not mangle the environment.

[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address

Are you guys using B2 or RC2 ? -- 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/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to

[Bug 1521279] Re: check_haproxy.sh is broken for openstack liberty's haproxy 1.5.14

** Also affects: keystone (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: cinder (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: glance (Ubuntu) Importance: Undecided Status: New ** No longer affects: glance

[Bug 1314887] Re: ifupdown hook is missing in upstart script

In order for this to be SRUed, it needs to be made compliant with https://wiki.ubuntu.com/StableReleaseUpdates (Please add a rational, test case, and regression potential to the description of this bug.) -- You received this bug notification because you are a member of Ubuntu Server Team, which

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu.

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

I just noticed this today. AFAICT, it only affects https to www.google.com and other Google subdomains (first noticed on docs.google.com). It does not affect Firefox. Odder still, I have two fully up-to-date (AFAICT) Xenial machines, both amd64. One of them connects to https://www.google.com

[Bug 1510703] Re: package cgmanager 0.36-2ubuntu5 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 102 zurück

apport says that something on your system removed /etc/init/cgmanager.conf and /etc/init/cgproxy.conf which then caused that upgrade error. ** Changed in: cgmanager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which

[Bug 1516989] Re: juju status broken

** Changed in: juju-core Assignee: Cheryl Jennings (cherylj) => Jesse Meek (waigani) -- 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/1516989 Title: juju status broken To

[Bug 1398068] Re: /sbin/cgmanager:alloc.c:315: Assertion failed in nih_free: ptr != NULL

Closing as won't fix since the error tracker is basically unusable right now and we've never had a single other report of this despite having cgmanager on a lot of armhf devices now (Ubuntu Core & Ubuntu Phone). I also went to look at my armhf builders for LXC where we spawn about 200 cgmanager

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

@barry.. Maybe do LiveCD tests on both of them to see if it's a configuration issue or if it might be hardware related. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1520568 Title:

[Bug 1516989] Re: juju status broken

Cheryl just pointed out that each unit needs to have a unit agent status doc and a workload (unit status) doc. So we can: 1 - generate a list of all the units 2 - query the status for each unit (not agent status) 3 - if it returns not found, then create the status -- You received this bug

[Bug 1521086] Re: Squid3 huge memory usage on 14.04

Finally, we found the root cause, it is kernel issue with specific version on ubuntu 14.04. We prepared new environment for testing, 3.3.8，3.5.11，2.7 on ubuntu 12.04 and 14.04. 3.3.8，3.5.11 on ubuntu 12.04 is ok 2.7 on ubuntu 14.04 is ok 3.3.8，3.5.11 on ubuntu 14.04 is abnormal. We tried

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

** Tags removed: haproxy ** Tags added: 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage

[Bug 1334958] Re: package haproxy 1.4.24-2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

** Changed in: haproxy (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1334958 Title: package haproxy 1.4.24-2 failed to install/upgrade:

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

** No longer affects: haproxy (Ubuntu) -- 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/1494141 Title: HAProxy 1.5 init script does not terminate processes To manage notifications

[Bug 1118160] Re: Please support flags for Secure / HttpOnly Cookies

HAProxy 1.5 is available in Wily, and 1.4.24 is available in Trusty, which should have this feature. ** Changed in: haproxy (Ubuntu) Importance: Undecided => Low ** Changed in: haproxy (Ubuntu) Status: Triaged => Fix Released ** Tags added: upgrade-software-version ** Information

[Bug 1308314] Re: incorrect balancing in weight value 256

** Changed in: haproxy (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1308314 Title: incorrect balancing in weight value 256 To manage

[Bug 1339801] Re: Illegal Instruction crash on startup with spread_checks in src/checks.c

** Changed in: haproxy (Ubuntu) Importance: Undecided => High ** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1339801 Title: Illegal Instruction crash on

[Bug 1521438] [NEW] Another MAX AVAIL bug unweighted OSD

Public bug reported: Unweighted OSDs (zero weighted), trigger another "MAX AVAIL 0" bug in OSD pools. Ref: http://tracker.ceph.com/issues/13840 ** Affects: ceph (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu

[Bug 1462495] Re: [sru] Init file does not respect the LSB spec.

** Changed in: haproxy (Ubuntu Trusty) Importance: Undecided => High ** Changed in: haproxy (Ubuntu Utopic) Importance: Undecided => High ** Changed in: haproxy (Ubuntu Utopic) Status: Fix Committed => Won't Fix ** Changed in: haproxy (Ubuntu Utopic) Status: Won't Fix => Fix

[Bug 1017854] Re: Precise: HAProxy has known defect (Slowness in establishing connections from ruby to Haproxy)

** Changed in: haproxy (Ubuntu) Importance: Undecided => Medium ** Changed in: haproxy (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu.

[Bug 1516989] Re: juju status broken

When targeting the upgrade step in 1.25 I cannot see a way to distinguish between 1. a correct agent statusDoc and 2. a unit statusDoc with a agent style id - as the id is the only distinguishing feature between the two. I imagine fwereade will hit this when writing the fix-it script.

[Bug 1521234] Re: ftbfs in xenial

This bug was fixed in the package squid3 - 3.3.8-1ubuntu17 --- squid3 (3.3.8-1ubuntu17) xenial; urgency=medium * --disable-strict-error-checking to fix FTBFS due to auto_ptr defined in unique pointer headers. (LP: #1521234). -- Dimitri John Ledkov Mon, 30

[Bug 1506244] Re: [SRU] support SSH key value over fingerprint for Azure

Verified. ** 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1506244 Title: [SRU] support SSH key value over

[Bug 1506244] Re: [SRU] support SSH key value over fingerprint for Azure

Verified. -- 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/1506244 Title: [SRU] support SSH key value over fingerprint for Azure To manage notifications about this bug go to:

[Bug 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

** Tags removed: verification-needed ** Tags added: verification-done-trusty -- 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/1506187 Title: [SRU] Azure: cloud-init should use VM

[Bug 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server

** Tags removed: verification-done-precise ** Tags added: verification-done -- 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: [SRU] cloud-init archive template

[Bug 1449099] Update Released

The verification of the Stable Release Update for bcache-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Bug 1449099] Re: [SRU] bcache-tools to trusty and precise

This bug was fixed in the package bcache-tools - 1.0.7-1~12.04.1 --- bcache-tools (1.0.7-1~12.04.1) precise; urgency=medium * Backport to Precise (LP: #1449099) -- LaMont Jones Mon, 09 Nov 2015 14:09:34 -0700 ** Changed in: bcache-tools (Ubuntu Precise)

[Bug 1356012] Re: maas incorrectly overmanages DNS reverse zones

** Also affects: maas/1.9 Importance: Undecided Status: New ** Changed in: maas/1.9 Status: New => Won't Fix ** Changed in: maas/1.9 Importance: Undecided => Critical ** Changed in: maas/1.9 Importance: Critical => Wishlist -- You received this bug notification because

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Same error here, and the package downgrade fixes it for now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1520568 Title: All queries fails when 'google' is used:

[Bug 1516989] Re: juju status broken

The fix for this is underway, and should be included in 1.25.2. William kindly put together a script to directly modify mongo to add in the missing statuses to work around this problem in the meantime. You can contact me directly to get the script until I figure out where to put it. I have

[Bug 1516989] Re: juju status broken

pr: http://reviews.vapour.ws/r/3279 ** Changed in: juju-core Status: Triaged => In Progress -- 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/1516989 Title: juju status

[Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Which IPs show the errors? It could be that different results may be due to different TLS terminators at Google. Figuring out one specific IP that demonstrates the issue may help (assuming Google hasn't done something crazy like anycast on their search IPs). -- You received this bug notification

  1   2   >