[Bug 1383869] Re: pollinate fails SSL validation

[Karl]

*** This bug is a duplicate of bug 1381359 ***
https://bugs.launchpad.net/bugs/1381359

This is happening still and can't seem to find a work around:

backdoor@maas-enlisting-node:~$ sudo pollinate
sudo: unable to resolve host maas-enlisting-node
Oct 14 14:06:51 maas-enlisting-node pollinate[1776]: client sent challenge to 
[https://entropy.ubuntu.com/]
Oct 14 14:06:51 maas-enlisting-node pollinate[1800]: ERROR: Network 
communication failed [60]\n14:06:51.133088 * Hostname was NOT found in DNS cache
  % Total % Received % Xferd Average Speed Time Time Time Current
 Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 014:06:51.137568 * Trying 
91.189.94.53...
14:06:51.271750 * Connected to entropy.ubuntu.com (91.189.94.53) port 443 (#0)
14:06:51.272710 * successfully set certificate verify locations:
14:06:51.272731 * CAfile: /etc/pollinate/entropy.ubuntu.com.pem
  CApath: /dev/null
14:06:51.272849 * SSLv3, TLS handshake, Client hello (1):
14:06:51.272884 } [data not shown]
14:06:51.404391 * SSLv3, TLS handshake, Server hello (2):
14:06:51.404432 { [data not shown]
14:06:51.417184 * SSLv3, TLS handshake, CERT (11):
14:06:51.417235 { [data not shown]
14:06:51.417754 * SSLv3, TLS alert, Server hello (2):
14:06:51.417776 } [data not shown]
14:06:51.417853 * SSL certificate problem: self signed certificate in 
certificate chain
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
14:06:51.417928 * Closing connection 0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollinate in Ubuntu.
https://bugs.launchpad.net/bugs/1383869

Title:
  pollinate fails SSL validation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1383869/+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 1310340] Re: live migration fails when use long hostname of a nova compute target host

[Adam Spiers]

Hi Melanie, just wondering why this change was abandoned?  Unless I
misunderstood, it seemed that the only objections to Patch Set 4 were
regarding implementation details, not against the approach.  Your way of
guarding against accidentally using the wrong non-unique hypervisor host
seems good to me, but maybe I'm missing something?  Thanks!

-- 
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/1310340

Title:
  live migration fails when use long hostname of a nova compute target
  host

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1310340/+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 1504354] Re: Invalid memory access on ap_server_config_defines

[Chris J Arges]

Hello Jeffrey, or anyone else affected,

Accepted apache2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apache2/2.4.7-1ubuntu4.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apache2 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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/1504354

Title:
  Invalid memory access on ap_server_config_defines

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1504354/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[John Johansen]

yes,
  UBUNTU: SAUCE: (no-up) apparmor: fix mount not handling disconnected 
paths 

is causing the regression. However reverting this fix will cause issues
for Bug 1496430, which was blocking a fix for a CVE.

The correct solution is to update the profile.

-- 
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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1506007] Re: Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests failing to run

[Barry Warsaw]

I'll do a local test and syncpackage if that passes.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007

Title:
  Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests
  failing to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-linecache2/+bug/1506007/+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 1506007] Re: Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests failing to run

[Barry Warsaw]

LGTM, syncing dropping the Ubuntu delta.

** Changed in: python-linecache2 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007

Title:
  Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests
  failing to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-linecache2/+bug/1506007/+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 1506007] Re: Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests failing to run

[Barry Warsaw]

This bug was fixed in the package python-linecache2 - 1.0.0-2

---
python-linecache2 (1.0.0-2) unstable; urgency=medium

  * Runs unit tests during build, thanks to a patch from James Page
(Closes: #795889).

 -- Thomas Goirand   Fri, 28 Aug 2015 15:46:28 +

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007

Title:
  Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests
  failing to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-linecache2/+bug/1506007/+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 1451537] Re: python-greenlet fails to build in trusty with updated python 2.7.9

[Launchpad Bug Tracker]

This bug was fixed in the package python-greenlet - 0.4.2-1ubuntu0.1

---
python-greenlet (0.4.2-1ubuntu0.1) trusty-proposed; urgency=medium

  * SRU: LP: #1451537.
  * Backport the test_leaks changes from 0.4.9.

 -- Matthias Klose   Fri, 02 Oct 2015 15:31:53 +0200

** Changed in: python-greenlet (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-greenlet in Ubuntu.
https://bugs.launchpad.net/bugs/1451537

Title:
  python-greenlet fails to build in trusty with updated python 2.7.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-greenlet/+bug/1451537/+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

Re: [Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Tiago Stürmer Daitx]

On the contrary, thanks for bringing that up. I was good to be made aware
of such problems. Just because it worked now on Precise and Trusty didn't
mean I should skip that check, as I might as well run into an obsolete or
deleted feature (not that upstart seem to have those). =)
On Oct 14, 2015 9:56 AM, "Robie Basak" <1073...@bugs.launchpad.net> wrote:

> On Wed, Oct 14, 2015 at 12:34:33PM -, Tiago Stürmer Daitx wrote:
> > According to http://upstart.ubuntu.com/cookbook/#stanzas-by-category
> > both "kill timeout" (all upstart versions) and "kill signal" (since
> > upstart 1.3) should be supported by upstart 1.5 in Precise so this SRU
> > should be fine.
>
> You're right. Sorry for the noise.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1073478
>
> Title:
>   [SRU] Update squid3 upstart script to kill it with SIGINT and wait
>   longer
>
> Status in squid3 package in Ubuntu:
>   Triaged
>
> Bug description:
>   [Impact]
>
>   Squid 3.1.19-1ubuntu3.12.04.3 on Precise and 3.3.8-1ubuntu6.3 on
>   Trusty do not clean up its PID file, causing logrotate to spit out an
>   error each night when cron runs it.
>
>   The underlying issue here is that the upstart script does not wait
>   long enough for squid3 to finish - one might also argue that it is
>   using the wrong signal if it expects squid to finish quickly.
>
>   By default, when squid3 receives a SIGTERM it will close the socket
>   for incoming connections and will wait for existing connections to
>   complete. The shutdown_lifetime directive configures how long it waits
>   before forcefully closing those open connections and it is set by
>   default to 30 seconds.
>
>   Current setting, SIGKILL happens after 5 seconds (which is the upstart
> default):
>   =
>   # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
>   Process 20865 attached - interrupt to quit
>0.00 --- SIGTERM (Terminated) @ 0 (0) ---
>0.000440 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
>0.000418 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>5.006483 +++ killed by SIGKILL +++
>
>   Killing squid with SIGKILL might lead to cache index corruption and a
>   very slow startup the next time it is started: http://lists.squid-
>   cache.org/pipermail/squid-users/2015-July/004752.html
>
>   The first way to avoid this is by increasing upstart's "kill timeout"
>   to a few seconds more then the "shutdown_lifetime" directive.
>
>   With "kill timeout 40" in upstart script, notice the pid file being
> unlinked (the ~30 seconds wait is due to the default value of
> shutdown_lifetime directive):
>   =
>   # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
>   Process 20805 attached - interrupt to quit
>0.00 --- SIGTERM (Terminated) @ 0 (0) ---
>0.000284 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
>0.000402 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>   31.611726 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>0.001792 --- SIGCHLD (Child exited) @ 0 (0) ---
>0.000247 rt_sigreturn(0x) = 63
>0.006027 unlink("/var/run/squid3.pid") = 0
>0.000539 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
>0.000387 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
>   Process 20805 detached
>
>   Still, this will unfortunately lead to a slow shutdown time as
>   reported in http://askubuntu.com/questions/18127/squid3-starts-and-
>   stops-slowly
>
>   To solve this it is better to issue a SIGINT instead of SIGTERM
>   (upstart default) by adding "kill signal SIGINT" to squid's upstart
>   script.
>
>   With "kill signal SIGINT", which does not wait on outstanding
> connections:
>   =
>   # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
>   Process 20891 attached - interrupt to quit
>0.00 --- SIGINT (Interrupt) @ 0 (0) ---
>0.000312 rt_sigreturn(0x2) = -1 EINTR (Interrupted system call)
>0.000237 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>1.123564 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>0.000754 --- SIGCHLD (Child exited) @ 0 (0) ---
>0.000103 rt_sigreturn(0x) = 0
>0.002031 unlink("/var/run/squid3.pid") = 0
>0.000154 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
>0.000142 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
>   Process 20891 detached
>
>   The whole stop process is very quick. The downside is that squid will
>   forcefully close all open connections immediately, but that was
>   already happening when SIGKILL was being issued before - so we are
>   actually keeping the same behavior as before and there are no bugs
>   complaining about it. And the PID file gets removed anyway.
>
>   The proposal is to add 

[Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Michael Terry]

OK, I've uploaded these to precise and trusty.  Will subscribe ubuntu-
sru and unsubscribe ubuntu-sponsors.

Does this need any adjusting in wily?  We don't use upstart anymore but
do ship a traditional init.d file.

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Michael Terry]

(And thanks so much for preparing these patches / SRU description,
Tiago!)

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Chris J Arges]

Hello Andy, or anyone else affected,

Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.7-0ubuntu0.8
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lxc (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Tiago Stürmer Daitx]

Thank you Michael!

We only need to touch Wily if we want to keep the upstart script updated
there as well, but as you said Wily no longer uses upstart. Updating it
would not change any behavior. So far I couldn't find any documentation
explaining how to proceed on this scenario, so I'm open to suggestions.
I'm also ok providing a debdiff for it if we decide to go that way. =)

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1189909] Re: dhcp-agent does always provide IP address for instances with re-cycled IP addresses.

[Ryan Moats]

** Package changed: quantum (CentOS) => centos

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quantum in Ubuntu.
https://bugs.launchpad.net/bugs/1189909

Title:
  dhcp-agent does always provide IP address for instances with re-cycled
  IP addresses.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1189909/+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 1451537] Update Released

[Chris J Arges]

The verification of the Stable Release Update for python-greenlet 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 regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-greenlet in Ubuntu.
https://bugs.launchpad.net/bugs/1451537

Title:
  python-greenlet fails to build in trusty with updated python 2.7.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-greenlet/+bug/1451537/+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 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Michael Terry]

Yeah, but is the bug present in the sysinit script?  I'm assuming not,
but it wouldn't hurt to verify.

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1505632] Re: FTBFS due to failing unit tests

[Launchpad Bug Tracker]

This bug was fixed in the package python-glance-store - 0.9.1-1ubuntu1

---
python-glance-store (0.9.1-1ubuntu1) wily; urgency=medium

  * debian/patches/fix_swift_unit_tests.patch:
- Cherry-pick fix from upstream for broken unit tests with swiftclient
  2.6.0 and higher (LP: #1505632).

 -- Łukasz 'sil2100' Zemczak   Wed, 14 Oct
2015 12:49:12 +0200

** Changed in: python-glance-store (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-glance-store in Ubuntu.
https://bugs.launchpad.net/bugs/1505632

Title:
  FTBFS due to failing unit tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-glance-store/+bug/1505632/+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 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Michael Terry]

** Also affects: squid3 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: squid3 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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

Re: [Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Robie Basak]

On Wed, Oct 14, 2015 at 05:49:12PM -, Tiago Stürmer Daitx wrote:
> We only need to touch Wily if we want to keep the upstart script updated
> there as well, but as you said Wily no longer uses upstart. Updating it
> would not change any behavior. So far I couldn't find any documentation
> explaining how to proceed on this scenario, so I'm open to suggestions.
> I'm also ok providing a debdiff for it if we decide to go that way. =)

IMHO, this doesn't need to be a priority for Ubuntu. In my next merge I
intend to drop the upstart script part of the Ubuntu delta anyway.

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file

[Marius Gedminas]

When Debian packages ship cron files, these usually test -x
/usr/bin/programname before executing it, to prevent errors in case the
package is removed but not purged.  I thought it was required by the
Debian policy, but I cannot find wording for it.  Maybe it was just a
courtesy.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1501217

Title:
  apt-get removing squid-deb-proxy-client leaves a stale config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[Huygens]

Hi Serge,

Sorry for the long delay in replying, I overlooked the email
notification.

Yes that is almost correct, I add previously installed the ppa:ubuntu-
lxc/lxd-stable (so the LXD one not ppa:ubuntu-lxc/stable as you
mentioned) in Vivid. But before doing the upgrade I installed the ppa-
purge tool and used it to remove this ppa (which was by the way the only
3rd party source on my system).

After a successful ppa-purge, I went on and did a do-release-upgrade
which then failed, or actually it did not complete successfully. So I
was still able to reboot the machine and Wily was the new system. LXC
was broken after the reboot. But I did: "apt update; apt upgrade; apt
full-upgrade" which fixed the it by properly installing LXC.

One thing was then missing from the upgrade process: because of the
failure with the LXC package, the cleaning at the end of the upgrade
(when executing do-release-upgrade) did not happen. So I had lots of
obsolete or dandling packages which I had to look for and remove
manually.

I guess a way to reproduce it is:

  1. Install Ubuntu 15.04
  2. Make sure the system is up to date: apt update; apt full-upgrade; reboot
  3. Install from the Ubuntu repository the following packages: lxc 
lxc-templates
  4. Install ppa:ubuntu-lxc/lxd-stable and install the following packages: lxc 
lxd lxc-templates
  5. (I don't think a reboot is necessary to proceed, but I'm not 100% sure)
  6. Install ppa-purge and remove the installed ppa from step 3 (this should 
install back the previous packages from the Ubuntu repos)
  7. Perform a release upgrade to Wily: di-release-upgrade -d
  8. Boom! (or at least it did that on 2 machines here!) :-)

-- 
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/1490110

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+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 1505961] [NEW] Internal Server Error: /dashboard/admin/volumes/ in Horizon

[Pavel]

Public bug reported:

Hi! I just installed new openstack and have problem with Horizon.

When I click in dashbord on links: Volumes, Overview or System
Information, in general everywhere where there is cinder, i have next
error:

[Wed Oct 14 15:00:27.185705 2015] [:error] [pid 8163] Internal Server Error: 
/dashboard/admin/volumes/
[Wed Oct 14 15:00:27.185773 2015] [:error] [pid 8163] Traceback (most recent 
call last):
[Wed Oct 14 15:00:27.185783 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in 
get_response
[Wed Oct 14 15:00:27.185789 2015] [:error] [pid 8163] response = 
wrapped_callback(request, *callback_args, **callback_kwargs)
[Wed Oct 14 15:00:27.185795 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec
[Wed Oct 14 15:00:27.185800 2015] [:error] [pid 8163] return 
view_func(request, *args, **kwargs)
[Wed Oct 14 15:00:27.185805 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in dec
[Wed Oct 14 15:00:27.185811 2015] [:error] [pid 8163] return 
view_func(request, *args, **kwargs)
[Wed Oct 14 15:00:27.185817 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/decorators.py", line 52, in dec
[Wed Oct 14 15:00:27.185822 2015] [:error] [pid 8163] return 
view_func(request, *args, **kwargs)
[Wed Oct 14 15:00:27.185827 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec
[Wed Oct 14 15:00:27.185832 2015] [:error] [pid 8163] return 
view_func(request, *args, **kwargs)
[Wed Oct 14 15:00:27.185837 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in dec
[Wed Oct 14 15:00:27.185892 2015] [:error] [pid 8163] return 
view_func(request, *args, **kwargs)
[Wed Oct 14 15:00:27.185899 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in 
view
[Wed Oct 14 15:00:27.185905 2015] [:error] [pid 8163] return 
self.dispatch(request, *args, **kwargs)
[Wed Oct 14 15:00:27.185911 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 89, in 
dispatch
[Wed Oct 14 15:00:27.185927 2015] [:error] [pid 8163] return 
handler(request, *args, **kwargs)
[Wed Oct 14 15:00:27.186152 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/views.py", line 146, in get
[Wed Oct 14 15:00:27.186165 2015] [:error] [pid 8163] context = 
self.get_context_data(**kwargs)
[Wed Oct 14 15:00:27.186172 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 107, in 
get_context_data
[Wed Oct 14 15:00:27.186217 2015] [:error] [pid 8163] context = 
super(MultiTableMixin, self).get_context_data(**kwargs)
[Wed Oct 14 15:00:27.186241 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/views.py", line 56, in 
get_context_data
[Wed Oct 14 15:00:27.186383 2015] [:error] [pid 8163] 
exceptions.handle(self.request)
[Wed Oct 14 15:00:27.186435 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/exceptions.py", line 364, in handle
[Wed Oct 14 15:00:27.186449 2015] [:error] [pid 8163] six.reraise(exc_type, 
exc_value, exc_traceback)
[Wed Oct 14 15:00:27.186627 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/views.py", line 54, in 
get_context_data
[Wed Oct 14 15:00:27.186969 2015] [:error] [pid 8163] 
context["tab_group"].load_tab_data()
[Wed Oct 14 15:00:27.186982 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/base.py", line 128, in 
load_tab_data
[Wed Oct 14 15:00:27.186989 2015] [:error] [pid 8163] 
exceptions.handle(self.request)
[Wed Oct 14 15:00:27.186996 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/exceptions.py", line 364, in handle
[Wed Oct 14 15:00:27.187002 2015] [:error] [pid 8163] six.reraise(exc_type, 
exc_value, exc_traceback)
[Wed Oct 14 15:00:27.187008 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/base.py", line 125, in 
load_tab_data
[Wed Oct 14 15:00:27.187157 2015] [:error] [pid 8163] tab._data = 
tab.get_context_data(self.request)
[Wed Oct 14 15:00:27.187168 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/base.py", line 465, in 
get_context_data
[Wed Oct 14 15:00:27.187174 2015] [:error] [pid 8163] self.load_table_data()
[Wed Oct 14 15:00:27.187180 2015] [:error] [pid 8163]   File 
"/usr/lib/python2.7/site-packages/horizon/tabs/base.py", line 449, in 
load_table_data
[Wed Oct 14 15:00:27.187185 2015] [:error] [pid 8163] table.data = 
data_func()
[Wed Oct 14 15:00:27.187198 2015] [:error] [pid 8163]   File 

[Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Robie Basak]

Note that there was an issue with php5 fpm (I think that was it) that we
can't ship a "kill" directive in an upstart job if someone can do a
release upgrade up to the version where that directive first appears.
Otherwise it gets done on the old upstart that does not support it and
break things. I can't find the bug reference right now, sorry, but it
should probably be checked against Precise.

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1499510] Re: Fix Typo in socket attribute name in TCPKeepAliveAdapter

[Michael Terry]

** Changed in: python-novaclient (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/1499510

Title:
  Fix Typo in socket attribute name in TCPKeepAliveAdapter

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1499510/+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 1499838] Please test proposed package

[Chris J Arges]

Hello Newell, or anyone else affected,

Accepted freeipmi into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/freeipmi/1.1.5-3ubuntu6.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838

Title:
  ipmi-locate causes synchronous external abort on ARM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[John Johansen]

To be specific I added the rule
  mount options=(rw,bind) /dev/pts/ptmx -> /dev/ptmx,

to the lxc-start profile

-- 
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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1506187] [NEW] Azure: cloud-init should use VM unique ID

[Stephen A. Zarkos]

Public bug reported:

The Azure datasource currently uses the InstanceID from the
SharedConfig.xml file.  On our new CRP stack, this ID is not guaranteed
to be stable and could change if the VM is deallocated.  If the
InstanceID changes then cloud-init will attempt to reprovision the VM,
which could result in temporary loss of access to the VM.

Instead cloud-init should switch to use the VM Unique ID, which is
guaranteed to be stable everywhere for the lifetime of the VM.  The VM
unique ID is explained here: https://azure.microsoft.com/en-us/blog
/accessing-and-using-azure-vm-unique-id/

In short, the unique ID is available via DMI, and can be accessed with
the command 'dmidecode | grep UUID' or even easier via sysfs in the file
"/sys/devices/virtual/dmi/id/product_uuid".

Steve

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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:
  Azure: cloud-init should use VM unique ID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1506187/+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 1385295] Re: use_syslog=True does not log to syslog via /dev/log anymore

[Chris J Arges]

For Ubuntu, Can you rebase this patch on the latest version of oslo.log?
When done please re-subscribe sponsors.

-- 
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/1385295

Title:
  use_syslog=True does not log to syslog via /dev/log anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.log/+bug/1385295/+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 1499838] Re: ipmi-locate causes synchronous external abort on ARM

[Chris J Arges]

Hello Newell, or anyone else affected,

Accepted freeipmi into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/freeipmi/1.1.5-3ubuntu3.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: freeipmi (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

** Changed in: freeipmi (Ubuntu Vivid)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838

Title:
  ipmi-locate causes synchronous external abort on ARM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+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 1486931] Re: [LTCTest][Opal][OP810] ipmitool 1.8.13-1ubuntu0.3 version is still not working for in-band HPM upgrade

[Steve Langasek]

BSWAP_16() is a non-standard declaration provided by the bswap.h header
file included in this patch.  The backported patch is missing an
 include in this file (lib/hpm2.c).

This appears to be a one-liner fix (see attached).  Hopefully this is
the only thing that was missed in the backport.

** Patch added: "ipmitool-missing-header.patch"
   
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1486931/+attachment/4494714/+files/ipmitool-missing-header.patch

** Changed in: ipmitool (Ubuntu Trusty)
   Status: Fix Committed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1486931

Title:
  [LTCTest][Opal][OP810] ipmitool 1.8.13-1ubuntu0.3 version is still not
  working for in-band HPM upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1486931/+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 1499838] Re: ipmi-locate causes synchronous external abort on ARM

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/freeipmi

** Branch linked: lp:ubuntu/trusty-proposed/freeipmi

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838

Title:
  ipmi-locate causes synchronous external abort on ARM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+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 1504781] Please test proposed package

[Martin Pitt]

Hello Andy, or anyone else affected,

Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.7-0ubuntu0.9
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1502604] Re: autopkgtests fail in LXC testbed

[Andy Whitcroft]

Also note that the first affected versions are those carrying the patch
below:

UBUNTU: SAUCE: (no-up) apparmor: fix mount not handling disconnected
paths

-- 
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/1502604

Title:
  autopkgtests fail in LXC testbed

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1502604/+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 1502604] Re: autopkgtests fail in LXC testbed

[Andy Whitcroft]

Note that this _only_ affects trusty.  All kernels in trusty are
affected.  linux-lts-vivid in trusty shows this behaviour where as linux
in vivid does not, as these are essentially identical it seems most
likely this is either an lxc profile issue or an appparmor userspace
issue.

-- 
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/1502604

Title:
  autopkgtests fail in LXC testbed

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1502604/+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 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Martin Pitt]

I suppose the recent kernel patch

UBUNTU: SAUCE: (no-up) apparmor: fix mount not handling disconnected
paths

which got backported to trusty causes this regression. As the same code
is present in later releases, I guess that in v/w lxc has an updated
apparmor profile which allows the operation that trusty's lxc is now
failing on due to the new apparmor violation?

-- 
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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+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 1502604] Re: autopkgtests fail in LXC testbed

[Andy Whitcroft]

Please ignore my previous two comments.  Wrong bug.

-- 
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/1502604

Title:
  autopkgtests fail in LXC testbed

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1502604/+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 1506007] [NEW] FTBFS due to unit tests failing to run

[Łukasz Zemczak]

Public bug reported:

As per the test-rebuild [1] for wily, this package now fails to build
from source due to some errors while running unit tests. Log:

===> Testing with python2.7 (python2)
Traceback (most recent call last):
  File "/usr/bin/python2-unit2", line 9, in 
load_entry_point('unittest2==1.1.0', 'console_scripts', 'unit2')()
  File "/usr/lib/python2.7/dist-packages/unittest2/__main__.py", line 18, in 
main_
main(module=None)
  File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 89, in 
__init__
self.parseArgs(argv)
  File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 119, in 
parseArgs
self._do_discovery([])
  File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 223, in 
_do_discovery
self.test = loader.discover(self.start, self.pattern, self.top)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 367, in 
discover
tests = list(self._find_tests(start_dir, pattern))
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
for test in path_tests:
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
for test in path_tests:
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 424, in 
_find_tests
full_path, pattern, namespace)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 479, in 
_find_test_path
msg % (mod_name, module_dir, expected_dir))
ImportError: 'test_linecache' module incorrectly imported from 
'/usr/lib/python2.7/dist-packages/linecache2/tests'. Expected 
'/«PKGBUILDDIR»/linecache2/tests'. Is this module globally installed?
debian/rules:37: recipe for target 'override_dh_auto_test' failed

** Affects: python-linecache2 (Ubuntu)
 Importance: Undecided
 Assignee: Łukasz Zemczak (sil2100)
 Status: In Progress


** Tags: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007

Title:
  FTBFS due to unit tests failing to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-linecache2/+bug/1506007/+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 1506007] Re: FTBFS due to unit tests failing to run

[Łukasz Zemczak]

** Description changed:

  As per the test-rebuild [1] for wily, this package now fails to build
  from source due to some errors while running unit tests. Log:
  
  ===> Testing with python2.7 (python2)
  Traceback (most recent call last):
-   File "/usr/bin/python2-unit2", line 9, in 
- load_entry_point('unittest2==1.1.0', 'console_scripts', 'unit2')()
-   File "/usr/lib/python2.7/dist-packages/unittest2/__main__.py", line 18, in 
main_
- main(module=None)
-   File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 89, in 
__init__
- self.parseArgs(argv)
-   File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 119, in 
parseArgs
- self._do_discovery([])
-   File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 223, in 
_do_discovery
- self.test = loader.discover(self.start, self.pattern, self.top)
-   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 367, in 
discover
- tests = list(self._find_tests(start_dir, pattern))
-   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
- for test in path_tests:
-   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
- for test in path_tests:
-   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 424, in 
_find_tests
- full_path, pattern, namespace)
-   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 479, in 
_find_test_path
- msg % (mod_name, module_dir, expected_dir))
+   File "/usr/bin/python2-unit2", line 9, in 
+ load_entry_point('unittest2==1.1.0', 'console_scripts', 'unit2')()
+   File "/usr/lib/python2.7/dist-packages/unittest2/__main__.py", line 18, in 
main_
+ main(module=None)
+   File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 89, in 
__init__
+ self.parseArgs(argv)
+   File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 119, in 
parseArgs
+ self._do_discovery([])
+   File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 223, in 
_do_discovery
+ self.test = loader.discover(self.start, self.pattern, self.top)
+   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 367, in 
discover
+ tests = list(self._find_tests(start_dir, pattern))
+   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
+ for test in path_tests:
+   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
+ for test in path_tests:
+   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 424, in 
_find_tests
+ full_path, pattern, namespace)
+   File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 479, in 
_find_test_path
+ msg % (mod_name, module_dir, expected_dir))
  ImportError: 'test_linecache' module incorrectly imported from 
'/usr/lib/python2.7/dist-packages/linecache2/tests'. Expected 
'/«PKGBUILDDIR»/linecache2/tests'. Is this module globally installed?
  debian/rules:37: recipe for target 'override_dh_auto_test' failed
+ 
+ [1] people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
+ rebuild-20151001-wily.html

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007

Title:
  FTBFS due to unit tests failing to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-linecache2/+bug/1506007/+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 1314887] Re: ifupdown hook is missing in upstart script

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/openvswitch

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1314887

Title:
  ifupdown hook is missing in upstart script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+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 1506238] Re: ship new public certificate

[Seth Arnold]

http://www.ubuntu.com/usn/usn-2709-2/

** Changed in: pollinate (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollinate in Ubuntu.
https://bugs.launchpad.net/bugs/1506238

Title:
  ship new public certificate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1506238/+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 1506257] [NEW] rpcapi version mismatch possible on upgrade

[Edward Hope-Morley]

Public bug reported:

The SRU recently landed for https://bugs.launchpad.net/nova/+bug/1349888
introduced a potential upgrade regression if nova services are not
upgraded all at once.

2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack RemoteError: Remote 
error: UnsupportedVersion Endpoint does not support RPC version 3.35
2015-10-14 20:45:00.778 10909 TRACE nova.api.openstack [u'Traceback (most 
recent call last):\n', u'  File 
"/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, 
in _dispatch_and_reply\nincoming.message))\n', u'  File 
"/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 185, 
in _dispatch\nraise UnsupportedVersion(version)\n', u'UnsupportedVersion: 
Endpoint does not support RPC version 3.35\n'].

Basically, if nova-compute services are updated after nova-api services
you will hit this issue if you perform volume operations. A simple
solution, if possible, is to upgrade nova-compute services so that they
are all in sync but I still want to remove the possibility for
regression while keeping the fix from 1349888. I will propose an SRU
shortly to resolve this.

** Affects: nova (Ubuntu)
 Importance: High
 Assignee: Edward Hope-Morley (hopem)
 Status: In Progress

** Changed in: nova (Ubuntu)
   Status: New => In Progress

** Changed in: nova (Ubuntu)
   Importance: Undecided => High

** Changed in: nova (Ubuntu)
 Assignee: (unassigned) => Edward Hope-Morley (hopem)

-- 
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/1506257

Title:
  rpcapi version mismatch possible on upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1506257/+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 1486033] Re: package libsnmp-base 5.7.2~dfsg-8.1ubuntu3.1 failed to install/upgrade: package libsnmp-base is already installed and configured

[Carlos]

*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

** Also affects: libnet-snmp-perl (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1486033

Title:
  package libsnmp-base 5.7.2~dfsg-8.1ubuntu3.1 failed to
  install/upgrade: package libsnmp-base is already installed and
  configured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnet-snmp-perl/+bug/1486033/+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 1499838] Re: ipmi-locate causes synchronous external abort on ARM

[dann frazier]

I've verified this no longer crashes on arm64, and that the output of
ipmi-locate on an x86 system (with a BMC) is identical before and after
this update.

** 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 freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1499838

Title:
  ipmi-locate causes synchronous external abort on ARM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1499838/+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 1506257] Re: rpcapi version mismatch possible on upgrade

[Edward Hope-Morley]

** Branch linked: lp:~hopem/nova/icehouse-lp1506257

-- 
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/1506257

Title:
  rpcapi version mismatch possible on upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1506257/+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 1501217] Re: apt-get removing squid-deb-proxy-client leaves a stale config file

[Robie Basak]

@Marius,

Sorry, I expected the original bug report to at a minimum tell me what
package version and Ubuntu release were affected, which is why I jumped
straight away to the standard template response asking for apport-
collect, as this would normally fill all of that information in. I
didn't notice that you had purged the package, and apport-collect them
won't be able to report its installed version, etc. I'm not sure about
your failure in comment #3.

@Rolf,

Thanks, that explains this bug. I agree that it's currently expected
behaviour, but I do think it's a little buggy that the config file is
still active after the package is removed. I wonder if it might be
possible for /etc/apt/apt.conf.d/30autoproxy to test for /usr/share
/squid-deb-proxy-client/apt-avahi-discover before calling it or
something?

Since there might be a little scope for user experience improvement
here, I'll leave this open until someone determines if this is possible
or not.

** Changed in: squid-deb-proxy (Ubuntu)
   Importance: Undecided => Low

** Summary changed:

- apt-get removing squid-deb-proxy-client leaves a stale config file
+ Removing squid-deb-proxy-client leaves a stale but active config file, 
breaking apt

** Changed in: squid-deb-proxy (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1501217

Title:
  Removing squid-deb-proxy-client leaves a stale but active config file,
  breaking apt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1501217/+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 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Tiago Stürmer Daitx]

Thanks for the feedback. Do you mean LP: #1272788 "php5-fpm upstart job
is not compatible with precise upstart" or LP: #1242376 "reload php5-fpm
crashes"?

That was one was caused because of the "reload" directive, only
introduced in upstart 1.10 while Precise only supports upstart 1.5.

According to http://upstart.ubuntu.com/cookbook/#stanzas-by-category
both "kill timeout" (all upstart versions) and "kill signal" (since
upstart 1.3) should be supported by upstart 1.5 in Precise so this SRU
should be fine.

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 1506007] Re: Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests failing to run

[Łukasz Zemczak]

Requesting a package sync from Debian. It has all Ubuntu changes and it
also has the fix for this FTBFS (addition of PYTHONPATH=. in
debian/rules). Could anyone sponsor the sync?

** Summary changed:

- FTBFS due to unit tests failing to run
+ Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests failing to run

** Description changed:

  As per the test-rebuild [1] for wily, this package now fails to build
- from source due to some errors while running unit tests. Log:
+ from source due to some errors while running unit tests. The Debian
+ version of this package has the bug fixed - requesting syncing.
+ 
+ Source package name: python-linecache2
+ Source package version number to sync: 1.0.0-2
+ Where to sync from: Debian testing
+ 
+ 
+ Log:
  
  ===> Testing with python2.7 (python2)
  Traceback (most recent call last):
    File "/usr/bin/python2-unit2", line 9, in 
  load_entry_point('unittest2==1.1.0', 'console_scripts', 'unit2')()
    File "/usr/lib/python2.7/dist-packages/unittest2/__main__.py", line 18, in 
main_
  main(module=None)
    File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 89, in 
__init__
  self.parseArgs(argv)
    File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 119, in 
parseArgs
  self._do_discovery([])
    File "/usr/lib/python2.7/dist-packages/unittest2/main.py", line 223, in 
_do_discovery
  self.test = loader.discover(self.start, self.pattern, self.top)
    File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 367, in 
discover
  tests = list(self._find_tests(start_dir, pattern))
    File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
  for test in path_tests:
    File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 433, in 
_find_tests
  for test in path_tests:
    File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 424, in 
_find_tests
  full_path, pattern, namespace)
    File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 479, in 
_find_test_path
  msg % (mod_name, module_dir, expected_dir))
  ImportError: 'test_linecache' module incorrectly imported from 
'/usr/lib/python2.7/dist-packages/linecache2/tests'. Expected 
'/«PKGBUILDDIR»/linecache2/tests'. Is this module globally installed?
  debian/rules:37: recipe for target 'override_dh_auto_test' failed
  
  [1] people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
  rebuild-20151001-wily.html

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-linecache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1506007

Title:
  Sync 1.0.0-2 from debian testing, fixes FTBFS due to unit tests
  failing to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-linecache2/+bug/1506007/+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 1506058] [NEW] [SRU] Openstack 2015.1.2 point release

[Chuck Short]

Public bug reported:

Hello everyone,

The OpenStack Stable Maintenance team is happy to announce the release
of the 2015.1.2 stable Kilo release. We have been busy reviewing and
accepting backported bugfixes to the stable/kilo branches according
to the criteria set at:

https://wiki.openstack.org/wiki/StableBranch

A total of 169 bugs have been fixed across all projects. These
updates to Kilo are intended to be low risk with no
intentional regressions or API changes. The list of bugs, tarballs and
other milestone information for each project may be found on Launchpad:

https://launchpad.net/ceilometer/kilo/2015.1.2
https://launchpad.net/cinder/kilo/2015.1.2
https://launchpad.net/glance/kilo/2015.1.2
https://launchpad.net/heat/kilo/2015.1.2
https://launchpad.net/horizon/kilo/2015.1.2
https://launchpad.net/ironic/kilo/2015.1.2
https://launchpad.net/keystone/kilo/2015.1.2
https://launchpad.net/neutron/kilo/2015.1.2
https://launchpad.net/nova/kilo/2015.1.2
https://launchpad.net/sahara/kilo/2015.1.2

Release notes may be found on the wiki:

https://wiki.openstack.org/wiki/ReleaseNotes/2015.1.2

** Affects: ceilometer (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: cinder (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: glance (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: heat (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: horizon (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: keystone (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: neutron (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: nova (Ubuntu)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: ceilometer (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: cinder (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: glance (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: heat (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: horizon (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: keystone (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: neutron (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Affects: nova (Ubuntu Vivid)
 Importance: Undecided
 Assignee: Chuck Short (zulcss)
 Status: New

** Also affects: glance (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: keystone (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ceilometer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cinder (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: heat (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: glance (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: keystone (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: ceilometer (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: cinder (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: heat (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: ceilometer (Ubuntu)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: ceilometer (Ubuntu Vivid)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: cinder (Ubuntu)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: cinder (Ubuntu Vivid)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: glance (Ubuntu)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: glance (Ubuntu Vivid)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: heat (Ubuntu)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: heat (Ubuntu Vivid)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed in: horizon (Ubuntu)
 Assignee: (unassigned) => Chuck Short (zulcss)

** Changed 

[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang

[Michael Terry]

> - reverse-dependencies don't have to be rebuilt for a security update to a
>   C library; even if an API does break, C revdeps can be left unbuildable
>   for a while with much less impact

I get that you're saying it's good because we don't have to waste
security-update-time fixing reverse-depends.  Which is a good point.
But it also sorta sounds like "in this scenario, the advantage of C
libraries is that we have unbuildable packages that we don't know
about".  So a bit of a mixed blessing.

> - since we're not using shared libraries (at this point), there's nothing
>   in the packaging of go packages (like sonames for C libraries) that
>   signals to proposed-migration that there's been an incompatible change
>   requiring a transition.

For incompatible changes requiring transitions, I thought the Go
convention was a new package name.  Like check.v1 or check.v2.  Which
would be a whole new package in Debian/Ubuntu.  Much like shared
libraries bumping sonames.

--

So adding synthesized dep8 tests or proposed-migration logic to confirm
no ftbfs by rebuilding Go reverse-dependencies are good ideas.  But I
maintain it's just as good an idea as doing the same thing for any other
package upload (checking reverse-depends for ftbfs).  The only
difference I see is Steve's point about the security team being faced
with ftbfs packages that they must now fix.  Normal package updates
wouldn't require a rebuild of all reverse-depends, so those would be
status quo.

1) So, since the security team is facing this, I'll leave this specific
question to them.  They didn't mention monitoring for ftbfs in their
list of requirements before, but maybe they'd like to?  I guess the
easiest route would be a golang-autopkgtest package like pitti
mentioned.

2) Am I being too carefree?  Do Go library minor updates tend to break
builds more often than C or Python libraries?  (Honest question, I'm not
a Go native.)  I had assumed Go folks have typical engineering
practices, but maybe the statically-linked nature of Go causes people to
play fast and loose with updates.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1267393/+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 1502363] Re: Linux bridge agent should include ebtables package and rootwrap rule

[Tom Fifield]

Still no updated package in the cloud archive

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1502363

Title:
  Linux bridge agent should include ebtables package and rootwrap rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1502363/+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 1445914] Update Released

[Chris J Arges]

The verification of the Stable Release Update for apache2 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 regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1445914

Title:
  Secure web socket proxy does not work in Apache 2.4.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1445914/+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 1486931] Re: [LTCTest][Opal][OP810] ipmitool 1.8.13-1ubuntu0.3 version is still not working for in-band HPM upgrade

[Chris J Arges]

This fails to build on powerpc (not ppc64el):

/bin/bash ../libtool --silent --tag=CC   --mode=link gcc  -g -O2 
-fno-strict-aliasing -Wreturn-type -I 
/lib/modules/3.13.0-65-powerpc64-smp/build/include   -o ipmitool ipmitool.o 
ipmishell.o ../lib/libipmitool.la plugins/libintf.la -lreadline -lncurses 
-ltinfo -lreadline -lncurses -ltinfo  -lcrypto
plugins/.libs/libintf.a(lt3-hpm2.o): In function `hpm2_get_capabilities':
/«PKGBUILDDIR»/lib/hpm2.c:125: undefined reference to `BSWAP_16'
plugins/.libs/libintf.a(lt3-hpm2.o): In function 
`hpm2_get_lan_channel_capabilities':
/«PKGBUILDDIR»/lib/hpm2.c:246: undefined reference to `BSWAP_16'
/«PKGBUILDDIR»/lib/hpm2.c:247: undefined reference to `BSWAP_16'
collect2: error: ld returned 1 exit status

https://launchpad.net/ubuntu/+source/ipmitool/1.8.13-1ubuntu0.4/+build/8028707

Is __builtin_bswap16 not available for powerpc gcc4.8?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/1486931

Title:
  [LTCTest][Opal][OP810] ipmitool 1.8.13-1ubuntu0.3 version is still not
  working for in-band HPM upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1486931/+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 1503608] Re: package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fe

[Ransom stark]

Not a bug, more of an installation support issue.

** Changed in: mysql-5.6 (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/mysql-5.6/+question/272417

-- 
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/1503608

Title:
  package mysql-server-5.6 5.6.19-0ubuntu0.14.04.1 [modified:
  usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1503608/+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 1498697] Re: Targets are not consistently shown with large numbers of targets

[Launchpad Bug Tracker]

This bug was fixed in the package tgt - 1:1.0.43-0ubuntu4.2

---
tgt (1:1.0.43-0ubuntu4.2) vivid; urgency=medium

  * debian/patches/fix-read-response-buffer.patch : Fix bug to read
the response buffer (LP: #1498697)

 -- Eric Desrochers   Wed, 30 Sep 2015
11:55:09 -0500

** Changed in: tgt (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1498697

Title:
  Targets are not consistently shown with large numbers of targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets

[Launchpad Bug Tracker]

This bug was fixed in the package tgt - 1:1.0.43-0ubuntu4.1~14.04.2

---
tgt (1:1.0.43-0ubuntu4.1~14.04.2) trusty; urgency=high

  * debian/patches/fix-read-response-buffer.patch : Fix bug to read
the response buffer (LP: #1498697)

 -- Eric Desrochers   Wed, 30 Sep 2015
11:41:52 -0500

** Changed in: tgt (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1498697

Title:
  Targets are not consistently shown with large numbers of targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Update Released

[Chris J Arges]

The verification of the Stable Release Update for tgt 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 regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
https://bugs.launchpad.net/bugs/1498697

Title:
  Targets are not consistently shown with large numbers of targets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1445914] Re: Secure web socket proxy does not work in Apache 2.4.7

[Launchpad Bug Tracker]

This bug was fixed in the package apache2 - 2.4.7-1ubuntu4.7

---
apache2 (2.4.7-1ubuntu4.7) trusty; urgency=medium

  * d/p/wstunnel-ssl.patch: mod_proxy_wstunnel: Fix the use of SSL
connections with the "wss:" scheme.  PR55320.  LP: #1445914
Submitted by: Alex Liu 

 -- Jeffrey Hutzelman   Thu, 10 Sep 2015
12:50:00 -0400

** Changed in: apache2 (Ubuntu Trusty)
   Status: Fix Committed => 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/1445914

Title:
  Secure web socket proxy does not work in Apache 2.4.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1445914/+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 1482765] Re: [MIR] neutron-vpnaas

[Jamie Strandboge]

This will not be reviewed in time for 15.10.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron-vpnaas in Ubuntu.
https://bugs.launchpad.net/bugs/1482765

Title:
  [MIR] neutron-vpnaas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron-vpnaas/+bug/1482765/+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

Re: [Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer

[Robie Basak]

On Wed, Oct 14, 2015 at 12:34:33PM -, Tiago Stürmer Daitx wrote:
> According to http://upstart.ubuntu.com/cookbook/#stanzas-by-category
> both "kill timeout" (all upstart versions) and "kill signal" (since
> upstart 1.3) should be supported by upstart 1.5 in Precise so this SRU
> should be fine.

You're right. Sorry for the noise.

-- 
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/1073478

Title:
  [SRU] Update squid3 upstart script to kill it with SIGINT and wait
  longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+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 305107] Re: mysql refuses to start because missing !includedir configuration directory

[Micah W.]

Ok, I think I ran into the same bug upgrading yesterday from 10.10 to
15.04.

I was able continue by doing three steps:

1. Adding the mysql Repos(may not be necessary)
https://dev.mysql.com/downloads/repo/

2. Tried doing apt-get install mysql-server and got this error:
"Setting up mysql-community-server (5.6.26-1ubuntu15.04) ...
mysqld: Can't read dir of '/etc/mysql/mysql.conf.d/' (Errcode: 13 - Permission 
denied)"

3. Removed apparmor
apt-get remove apparmor apparmor-utils

4. Did apt-get install mysql-server -> This time it worked!

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/305107

Title:
  mysql refuses to start because missing !includedir configuration
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/305107/+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 1314887] Re: ifupdown hook is missing in upstart script

[Launchpad Bug Tracker]

This bug was fixed in the package openvswitch - 2.4.0-0ubuntu3

---
openvswitch (2.4.0-0ubuntu3) wily; urgency=medium

  [ Brian Turek ]
  * Add ifupdown hooks for upstart script. (LP: #1314887)

 -- Chris J Arges   Wed, 14 Oct 2015
13:51:13 -0500

** Changed in: openvswitch (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1314887

Title:
  ifupdown hook is missing in upstart script

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1314887/+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 1457517] Update Released

[Chris J Arges]

The verification of the Stable Release Update for nova 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 regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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/1457517

Title:
  Unable to boot from volume when flavor disk too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1457517/+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 1506058] Re: [SRU] Openstack 2015.1.2 point release

[Launchpad Bug Tracker]

** Branch linked: lp:~zulcss/nova/kilo-2015.1.2

-- 
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/1506058

Title:
  [SRU] Openstack 2015.1.2 point release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1506058/+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 1504354] Re: Invalid memory access on ap_server_config_defines

[Robie Basak]

Uploaded; now awaiting SRU team review.

** Changed in: apache2 (Ubuntu Trusty)
   Status: Triaged => In Progress

-- 
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/1504354

Title:
  Invalid memory access on ap_server_config_defines

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1504354/+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 1465935] Please test proposed package

[Chris J Arges]

Hello Li, or anyone else affected,

Accepted qemu into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.2+dfsg-
5expubuntu9.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1465935

Title:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+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 1465935] Re: kvm_irqchip_commit_routes: Assertion `ret == 0' failed

[Chris J Arges]

Hello Li, or anyone else affected,

Accepted qemu into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/2.0.0+dfsg-
2ubuntu1.20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: qemu (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: qemu (Ubuntu Vivid)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1465935

Title:
  kvm_irqchip_commit_routes: Assertion `ret == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1465935/+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 1457517] Re: Unable to boot from volume when flavor disk too small

[Launchpad Bug Tracker]

This bug was fixed in the package nova - 1:2015.1.1-0ubuntu2

---
nova (1:2015.1.1-0ubuntu2) vivid; urgency=medium

  [ Corey Bryant ]
  * d/rules: Prevent dh_python2 from guessing dependencies.

  [ Liang Chen ]
  * d/p/not-check-disk-size.patch: Fix booting from volume error
when flavor disk too small (LP: #1457517)

 -- Corey Bryant   Thu, 13 Aug 2015 15:13:43
-0400

** Changed in: nova (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

-- 
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/1457517

Title:
  Unable to boot from volume when flavor disk too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1457517/+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 1505590] Re: netbios name truncating doesn't work

[Chris J Arges]

Hello Sebastien, or anyone else affected,

Accepted samba into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-
1ubuntu2.14.04.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: samba (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: samba (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1505590

Title:
  netbios name truncating doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1505590/+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 1298921] Re: cloud-init should give up on 404 errors

[Scott Moser]

Thiago,
  the CloudSigma datasource is the one that is doing the http requests listed 
above.  That datasource cannot be configured with timeout.  It should be a 
fairly easy fix to add that.

Note, though that if you're hitting the cloudsigma datasource, you are
likely running on cloudsigma or there is another bug.

the cloudsigma code in trunk at the moment does a 'is_running_cloudsigma' check 
that should have very few false positives.  See: 
  
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/DataSourceCloudSigma.py#L45

it should only return True if 'system-product-name' from the host-
provided dmi data has 'cloudsigma' in it.

-- 
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/1298921

Title:
  cloud-init should give up on 404 errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1298921/+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 1506238] [NEW] ship new public certificate

[Seth Arnold]

*** This bug is a security vulnerability ***

Public security bug reported:

USN-2709-1 supplied a new certificate but did not include the entire
certificate chain. This is similar to bugs #1304777 #1381359 #1483762.

Robie Basak provided debdiffs, http://paste.ubuntu.com/12774324/ and
http://paste.ubuntu.com/12774331/

Thanks

** Affects: pollinate (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pollinate in Ubuntu.
https://bugs.launchpad.net/bugs/1506238

Title:
  ship new public certificate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1506238/+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 592303] Re: rsync transfer failed: File name too long (36)

[Damien barifon]

*** This bug is a duplicate of bug 344878 ***
https://bugs.launchpad.net/bugs/344878

Try to long path tool. It is very helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/592303

Title:
  rsync transfer failed: File name too long (36)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/592303/+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