date:20140902

[Bug 1301132] Re: oslo-messaging-zmq-receiver cannot recive any messages

2014-09-02 Thread James Page

** Also affects: oslo.messaging (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: oslo.messaging (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: oslo.messaging (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: oslo.messaging (Ubuntu Utopic)
   Status: New = Fix Released

** Changed in: oslo.messaging (Ubuntu Trusty)
   Status: New = Triaged

** Changed in: oslo.messaging (Ubuntu Trusty)
   Importance: Undecided = High

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

Title:
  oslo-messaging-zmq-receiver cannot recive any messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1301132/+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 1364298] [NEW] mysql plugins fail on mysql 5.5/5.6

2014-09-02 Thread Hans-Joachim Kliemeck

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - 
About Ubuntu
Ubuntu 14.04 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
munin-plugins-core:
  Installed: 2.0.19-3munin-plugins-core:
  Installed: 2.0.19-3
3) What you expected to happen / 4) What happened instead

Several of the MySQL monitors give errors like the following when used
with Mysql 5.5/5.6 and multiple mysql bufferpools on trusty:

root@server:~# /etc/munin/plugins/mysql_connections 
Unknown section: INDIVIDUAL BUFFER POOL INFO at 
/etc/munin/plugins/mysql_connections line 1098.

As far as I can tell, this issue has been addressed upsteam:

* https://github.com/munin-monitoring/munin/pull/109/

These fixes were included in the 2.1.3 release of Munin, but sadly, trusty only 
include 2.0.19.
https://github.com/munin-monitoring/munin/commit/8abb3faf7865af125ecc18b4feece35c59c90fd9

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


** Tags: munin mysql mysql55 mysql56

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

Title:
  mysql plugins fail on mysql 5.5/5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1364298/+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 1257186] Re: memory leakage messages (no talloc stackframe)

2014-09-02 Thread goofrider

I checked Samba changelog, the patch was included in Samba 4.1.10. It's
scheduled for release with Trusty 14.04.2 can manually pull the Samba
package from Utopic (currently @ 4.1.11) now. You can also use this PPA,
which tracks the latest Samba upstream releases.

https://launchpad.net/~martinx/+archive/ubuntu/ig


From http://www.samba.org/samba/history/samba-4.1.10.html


BUG 8449: Simple use case results in no talloc stackframe around, leaking
  memory error.)

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

Title:
  memory leakage messages (no talloc stackframe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1257186/+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 1286209] Fix proposed to neutron (master)

2014-09-02 Thread OpenStack Infra

Fix proposed to branch: master
Review: https://review.openstack.org/118321

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

Title:
  unhandled trace if no namespaces in metering agent

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1286209/+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 1357229] Re: [SRU] 2.0.2 stable update

2014-09-02 Thread Launchpad Bug Tracker

This bug was fixed in the package openvswitch - 2.0.2-0ubuntu0.14.04.1

---
openvswitch (2.0.2-0ubuntu0.14.04.1) trusty; urgency=medium

  * New upstream stable release (LP: #1357229):
- Includes fix for SIGSEGV in nl_attr_get_size() due to use of
  de-allocated object during flow teardown (LP: #1352570).
 -- James Page james.p...@ubuntu.com   Fri, 15 Aug 2014 09:05:46 +0100

** Changed in: openvswitch (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 openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1357229

Title:
  [SRU] 2.0.2 stable update

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

2014-09-02 Thread Scott Kitterman

The verification of the Stable Release Update for openvswitch 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 openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1352570

Title:
  ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1352570/+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 1352570] Re: ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()

2014-09-02 Thread Launchpad Bug Tracker

This bug was fixed in the package openvswitch - 2.0.2-0ubuntu0.14.04.1

---
openvswitch (2.0.2-0ubuntu0.14.04.1) trusty; urgency=medium

  * New upstream stable release (LP: #1357229):
- Includes fix for SIGSEGV in nl_attr_get_size() due to use of
  de-allocated object during flow teardown (LP: #1352570).
 -- James Page james.p...@ubuntu.com   Fri, 15 Aug 2014 09:05:46 +0100

** Changed in: openvswitch (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 openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1352570

Title:
  ovs-vswitchd crashed with SIGSEGV in nl_attr_get_size()

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

2014-09-02 Thread Scott Kitterman

The verification of the Stable Release Update for openvswitch 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 openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1357229

Title:
  [SRU] 2.0.2 stable update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1357229/+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 1346166] Re: [SRU] 0.80.5 point release

2014-09-02 Thread James Page

No issues seen on ServerStack, marking verification done.

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

Title:
  [SRU] 0.80.5 point release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1346166/+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 1361357] Re: metadata service performance regression ~100x

2014-09-02 Thread Scott Moser

** No longer affects: nova (Ubuntu)

** No longer affects: nova

** Also affects: neutron
   Importance: Undecided
   Status: New

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

** No longer affects: nova (Ubuntu Trusty)

** No longer affects: nova (Ubuntu Utopic)

** Changed in: neutron
   Status: New = Confirmed

** Changed in: neutron (Ubuntu Trusty)
   Status: New = Confirmed

** Changed in: neutron (Ubuntu Utopic)
   Status: New = Confirmed

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

Title:
  metadata service performance regression ~100x

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1361357/+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 1361357] Re: metadata service performance regression ~8x

2014-09-02 Thread Scott Moser

** Summary changed:

- metadata service performance regression ~100x
+ metadata service performance regression ~8x

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

Title:
  metadata service performance regression ~8x

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1361357/+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 1361357] Re: metadata service performance regression ~8x

2014-09-02 Thread Scott Moser

I updated the description with a better diagnosis of the problem, as the
first was way off, and only would cause confusion.

** Description changed:

- The fix for bug 1325128 [1] included changes to the metadata service
- seen at:
- trunk[2]: 4a60c6a655006b2882331844664fac5cf67c5f34
- icehouse [3]: 9f59ca751f1a392ef24d8ab73a7bf5ce9655017e
+ A change was made to the neutron portion of the nova metadata service to
+ disable caching. This ends up causing a all hits to the nova metadata
+ service to generate messages to retrieve data from neutron. Doing so
+ makes a crawl of the metadata service take at least 8x longer than it
+ did. cloud-init crawls the metadata service during boot. The end
+ result is that instances boot significantly slower than they did
+ previously.

- The new code is around 100x slower. That slow down causes
- excessive load on the metadata server if an instance crawls the metadata
- service (which generates dozens of http requests).
+ The commits are marked as having fixed bug 1276440 [1].
+ The commits are:
+ icehouse: d568fee34be36ca17a9124fe6539f62d702d6359 [2]
+ trunk: 3faea81c6029033c85cefd6e98d7a3e719e858f5 [3]

- Both cloud-init and cirros's boot code crawl that meta-data service. The
- end result is linux instances boot time is dramatically affected. A
- typical Ubuntu boot time will be 10 seconds to executing user code, but
- after this regression, I'm seeing boots in the range of 30 to 45 seconds.
-
- While the fix is exactly intended to slow things down to improve
- security, the performance regression seems significant enough to
- address.
-
- --
- [1] http://pad.lv/1325128
- [2]
https://git.openstack.org/cgit/openstack/nova/commit/?id=4a60c6a655006b2882331844664fac5cf67c5f34
- [3]
https://git.openstack.org/cgit/openstack/nova/commit/?id=4a60c6a655006b2882331844664fac5cf67c5f34
+ [1] http://pad.lv/1276440
+ [2]
https://github.com/openstack/neutron/commit/d568fee34be36ca17a9124fe6539f62d702d6359
+ [3]
https://github.com/openstack/neutron/commit/423ca756af10e10398636d6d34a7594a4fd4bc87

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

Title:
metadata service performance regression ~8x

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1361357/+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 1363832] Re: [utopic] fails to build template container -- ubuntu-cloudimg-query fails

2014-09-02 Thread Martin Pitt

I think this deserves some priority, as it seems this completely breaks
cloud-utils/juju on utopic. The autopkgtest doesn't spot this because it
just does bootstrap, but for juju-local bootstrapping doesn't really
do much. The autopkgtest should also actually deploy something, to cover
building the template and the service container.

Tentatively assigning to Scott, can you please assign this to someone
appropriate?

** Also affects: cloud-utils (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: juju-core (Ubuntu Utopic)
   Importance: Undecided
   Status: Invalid

** Changed in: cloud-utils (Ubuntu Utopic)
   Importance: Undecided = High

** Changed in: cloud-utils (Ubuntu Utopic)
 Assignee: (unassigned) = Scott Moser (smoser)

** Description changed:

+ TL;DR: Utopic's ca-certificates don't cover the cert we are using to
+ sign our cloud images and their catalogs, and utopic's wget now fails on
+ a cert which can't be validated. This completely breaks ubuntu-cloudimg-
+ query and lxc-ubuntu-cloud.
+ 
+ Original report below:
+ --- 
+ 
  I tried the local provider again on current utopic, and today it fails
  on creating containers:
  
  - Start from a clean slate: no *juju* containers (I do have some
  containers for other work, though), no ~/.juju, etc. I follow
  https://juju.ubuntu.com/docs/getting-started.html and
  https://juju.ubuntu.com/docs/config-local.html
  
  - sudo apt install juju-core juju-local
    juju generate-config
    juju switch local
  
  - As I have $HOME on ecryptfs, I follow the documentation and use a
  separate juju root:
  
    sudo mkdir /scratch/juju
    sudo chown martin:martin /scratch/juju/
  
    Now I edit ~/.juju/environments.yaml in the local section to have
  root-dir: /scratch/juju and default-series: trusty.
  
    I also apply a workaround for bug 1290920:
    lrwxrwxrwx 1 root root 12 Jun 11 21:55 /var/lib/lxc - /scratch/lxc
  
  - Now bootstrap, this apparently works well:
  
  $ juju bootstrap
  uploading tools for series [precise trusty utopic]
  [sudo] password for martin:
  Logging to /scratch/juju/cloud-init-output.log on remote host
  Bootstrapping Juju machine agent
  Starting Juju machine agent (juju-agent-martin-local)
  
  This took maybe 10 seconds. /scratch/juju/cloud-init-output.log contains
  no ERROR, and ends with juju-agent-martin-local start/running,
  process 3997, so this seems fine. But I'll attach the log anyway. Note
  that this did *not* create any extra container; sudo lxc-ls --fancy
  does not show me anything new.
  
  $ juju status
  environment: local
  machines:
    0:
  agent-state: started
  agent-version: 1.20.5.1
  dns-name: localhost
  instance-id: localhost
  series: utopic
  state-server-member-status: has-vote
  services: {}
  
  - Now I try to deploy the GUI:
  
  $ juju deploy juju-gui
  Added charm cs:trusty/juju-gui-5 to the environment.
  
  (Returned after ~ 5 s)
  
  $ juju status
  environment: local
  machines:
    0:
  agent-state: started
  agent-version: 1.20.5.1
  dns-name: localhost
  instance-id: localhost
  series: utopic
  state-server-member-status: has-vote
    1:
  agent-state-info: container failed to start
  instance-id: pending
  series: trusty
  services:
    juju-gui:
  charm: cs:trusty/juju-gui-5
  exposed: false
  units:
    juju-gui/0:
  agent-state: pending
  machine: 1
  
  This created a new container:
  juju-trusty-lxc-template  STOPPED  - - -   NO
  
  But it is basically empty, except for a new log dir:
  
  $ find /scratch/lxc/juju-trusty-lxc-template/
  /scratch/lxc/juju-trusty-lxc-template/
  /scratch/lxc/juju-trusty-lxc-template/config
  /scratch/lxc/juju-trusty-lxc-template/rootfs
  /scratch/lxc/juju-trusty-lxc-template/rootfs/var
  /scratch/lxc/juju-trusty-lxc-template/rootfs/var/log
  /scratch/lxc/juju-trusty-lxc-template/rootfs/var/log/juju
  
  The first error in /scratch/juju/log/machine-0.log is
  
  2014-09-01 06:36:47 ERROR juju.worker runner.go:218 exited api: unable
  to connect to wss://localhost:17070/
  
  but it seems to retry and succeed a bit later:
  
  2014-09-01 06:36:50 INFO juju.state.api apiclient.go:176 connection
  established to wss://localhost:17070/
  
  then it just ends with
  
  2014-09-01 06:39:19 ERROR juju.container.lxc clonetemplate.go:167 container 
failed to start: container failed to start
  2014-09-01 06:39:19 ERROR juju.provisioner provisioner_task.go:418 cannot 
start instance for machine 1: container failed to start
  
  I'll also attach the full file. So it seems it fails very early on to
  create containers, this doesn't seem very charm specific. But just to
  make sure, I destroyed the juju service and machine (which didn't
  destroy the container, I did that manually) and service, and tried to
  juju deploy mysql, but with the exact same result.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10

98 matches

Mail list logo